bad error reporting on failed CONNECT
@mjog
Submitted by Michael Gratton Assigned to libsoup-maint@gnome.bugs
Link to original bug (#684418)
Description
Using the Soup GNOME features, when a HTTPS proxy is set to something that does not match the HTTP proxy, all HTTPS connections result in a SoupMessage.response_body.data being null.
To reproduce:
-
"apt-get install polipo" (or find a proxy supporting both HTTP and HTTPS)
-
In gnome-control-center, set both HTTP and HTTPS proxy to localhost:8123 (or your proxy address)
-
Fetch https://duckduckgo.com/?q=foo using Soup w/ the GNOME feature type (Ephy 3.5.4 works here)
-
Observe the page load succeeds
-
Change the HTTP proxy to be something other than the HTTPS proxy
-
Observe the page load fails (in Ephy, results in a download of an empty file)
Note that GProxy is returning the correct proxy address in both cases, so I assume Soup's GNOME proxy resolver is at issue here.
Version: 2.39.x