GNOME Bugzilla – Bug 726960
Evolution can not open access exchange server via proxy
Last modified: 2015-04-08 06:58:58 UTC
Created attachment 272764 [details] This is an export from wireshark showing what happens on the network. Hi, I have upgraded my evolution to 3.10.4 hoping that newer version will work better, but I still have problems connecting to exchange ews via proxy. I have two identical setups of evolution. One can connect without proxy and another can connect only via proxy. The one with proxy connection reports: ----------------------------------------------------------- Failed to open folder. The reported error was "No response: Cannot connect to destination (rea.abcd.ef)". ----------------------------------------------------------- The identical setup without proxy works fine. I have transferred accounts from one setup to another with "Backup/Restore Evolution data" to make sure settings are the same. Unfortunately I need evolution on computer where proxy is mandatory. Our exchange server also has a certificate with custom CA. I have added this CA to my setup and it works fine. I can connect to exchange server with browser without problem. Wireshark network recording attached to this report shows how evolution connects to proxy but immediately after that FIN, ACK is issued on evolution side and connection breaks. After that evolution reports an error opening folder. If I select "Send/Receive" it stays on infinitely and nothing happens.
I updated Ubuntu to 14.04 which is still a development release. I just found out that evolution is version 3.10.4, but evolution-ews is version 3.10.2. I guess I should wait for final Ubuntu 14.04 to get all correct versions of libraries and all other software.
Thanks for a bug report. If I look at yours bug #698728, then I'd say it also depends on the libsoup version. What is that yours, please? Maybe we should rather reopen the former bug report, if the changes from there have any regression, though the only thing the evolution-ews does is that it passes a URL of a proxy to be used by libsoup, and all the rest is up to the libsoup itself. By the way, do you have configured the proxy in Evolution (Edit->Preferences->Network Preferences->Manual...) or you use a system settings for a proxy? The version mismatch between evolution and evolution-ews might not be a problem, though the code itself tries to keep them in sync.
Hi, it seems that I have libsoup 2.44. That is my output of installed libsoup packages: ii gir1.2-soup-2.4 2.44.2-1ubuntu2 amd64 GObject introspection data for the libsoup HTTP library ii libsoup-gnome2.4-1:amd64 2.44.2-1ubuntu2 amd64 HTTP library implementation in C -- GNOME support library ii libsoup-gnome2.4-dev 2.44.2-1ubuntu2 amd64 HTTP library implementation in C -- GNOME support development files ii libsoup2.4-1:amd64 2.44.2-1ubuntu2 amd64 HTTP library implementation in C -- Shared library ii libsoup2.4-dbg 2.44.2-1ubuntu2 amd64 HTTP library implementation in C -- debugging symbols ii libsoup2.4-dev 2.44.2-1ubuntu2 amd64 HTTP library implementation in C -- Development files ii libsoup2.4-doc 2.44.2-1ubuntu2 all HTTP library implementation in C -- API Reference I have manual configuration of proxy. I have now tried the system settings proxy and the result is identical.
Thanks for the update. Maybe if you can do one more test, get debugging directly from the libsoup, which you can do when you run evolution like this: $ EWS_DEBUG=2 evolution &>log.txt The log will contain raw communication between the client and the server, exposing server addresses and all around it, thus remove any private information from it (like also Authenticate/Authentication-related headers). Dan, could you give some advice from the libsoup side, please? It seems there's something non-working from our updates on bug #698728.
how exactly are you configuring the proxy, and exactly what value(s) are you setting it to?
Created attachment 273136 [details] This log output with EWS_DEBUG=2
Created attachment 273137 [details] Screenshot of proxy settings
I attached the log output and proxy settings screenshot.
ping Dan, maybe related to bug #733876 now?
bug 733876 is about non-http apps using http proxies. It doesn't apply to libsoup. The screenshot shows that this is using evolution-defined proxy settings, so it's going through ESourceProxy... maybe a bug there? Or in how evolution-ews connects it to the session?
Oops, wrong shot. The other bug I recall is bug #724316, which, according to NEWS file, didn't reach libsoup 2.44.x, but only 2.45.90+.
oh, quite possibly, yes
Marko, do you have access to libsoup 2.46.0 or later, please? It would be good to test with it, to know whether the fix from comment #11 fixed the proxy issue or not.
I think I have libsoup 2.46, but I don't have access via proxy any more.
Thanks for the update. I hoped we would be able to confirm the fix, but that's okay. let's consider this fixed (I do not have a proxy too). *** This bug has been marked as a duplicate of bug 724316 ***