Firefox uses Socks proxy from Gnome network proxy
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mozilla Firefox |
Won't Fix
|
Medium
|
|||
firefox (Ubuntu) |
Triaged
|
Medium
|
Unassigned |
Bug Description
1)
Description: Ubuntu 11.04
Release: 11.04
2)
firefox:
Installed: 5.0+build1+
Candidate: 5.0+build1+
Version table:
*** 5.0+build1+
500 http://
500 http://
100 /var/lib/
4.
500 http://
3)
Gnome Network Proxy has different settings for HTTP/HTTPS and SOCKS proxies.
And Firefox proxy settings are set to use System proxy settings.
While browsing, Firefox must use HTTP/HTTPS proxy.
4)
Firefox actually uses SOCKS proxy, instead of HTTP/HTTPS.
NB... If using those proxy settings in Firefox itself, it uses HTTP/HTTPS...
I guess, it must use HTTP also from System settings as well...
Changed in firefox: | |
importance: | Unknown → Medium |
status: | Unknown → Confirmed |
Changed in firefox: | |
status: | Confirmed → Won't Fix |
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.5) Gecko/20091105 Fedora/3.5.5-1.fc11 Firefox/3.5.5
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.5) Gecko/20091105 Fedora/3.5.5-1.fc11 Firefox/3.5.5
In the case of using "system" proxy settings and /system/ http_proxy/ use_same_ proxy is not set, the SOCKS proxy is used in preference to the HTTP or FTP proxy.
This behaviour is wrong because the protocol specific protocols are more specific. For example, if one wants to specify an HTTP proxy but fall back to a SOCKS proxy for other protocols.
The relevant code is in nsUnixSystemPro xySettings: :GetProxyFromGC onf(). It would be better (and simpler) IMO to only set the type to SOCKS if there is no protocol specific proxy setting
Reproducible: Always
Steps to Reproduce:
1. On a network with a suitable http proxy <proxy host> Set system proxy settings (using Gconf Editor, or Network Proxy Preferences applet etc) to:
/system/ http_proxy/ host <proxy host> http_proxy/ port <proxy port> http_proxy/ use_http_ proxy true http_proxy/ use_same_ proxy false proxy/socks_ host <invalid hostname>
/system/
/system/
/system/
/system/
2. Try to connect to a well known public web site
Actual Results:
Connection fails.
Expected Results:
Connection should have succeeded
As far as I can see, the logic for handling manually set proxies in the preferences UI is the same as I am proposing for system preferences.