HTTPS connections fail when GNOME HTTP/HTTPS proxy config differ
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
libsoup |
Expired
|
Critical
|
|||
epiphany-browser (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
libsoup2.4 (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
[From upstream bug: https:/
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.
To reproduce:
1. "apt-get install polipo" (or find a proxy supporting both HTTP and HTTPS)
2. In gnome-control-
your proxy address)
3. Fetch https:/
(Ephy 3.5.4 works here)
4. Observe the page load succeeds
5. Change the _HTTP_ proxy to be something other than the HTTPS proxy
6. Fetch https:/
7. 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.
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: libsoup-gnome2.4-1 2.39.92-0ubuntu1
ProcVersionSign
Uname: Linux 3.5.0-15-generic x86_64
ApportVersion: 2.5.2-0ubuntu3
Architecture: amd64
Date: Thu Sep 20 13:34:07 2012
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
SourcePackage: libsoup2.4
UpgradeStatus: Upgraded to quantal on 2012-09-18 (1 days ago)
Changed in libsoup: | |
importance: | Unknown → Critical |
status: | Unknown → New |
Changed in libsoup: | |
status: | New → Confirmed |
Changed in libsoup: | |
status: | Confirmed → Expired |
Status changed to 'Confirmed' because the bug affects multiple users.