513663 - Use system proxy settings doesn't work on Mac OS X

Status: RESOLVED WORKSFORME

(Core :: Networking, defect)

Description

[Michal Majchrowicz]

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; pl; rv:1.9.1.2) Gecko/20090729 Firefox/3.5.2
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; pl; rv:1.9.1.2) Gecko/20090729 Firefox/3.5.2

Use system proxy settings doesn't work on Mac OS X.

Reproducible: Always

Steps to Reproduce:
1. Set proxy settings in Mac OS X's Preferences (I tried socks)
2. Set Use system proxy in Firefox
3. Try to open any web page (whatismyip.com is a good example)
Actual Results:  
Whatismyip.com shows the ip of the machine you are useing not the proxy.

Expected Results:  
See the ip of proxy.

Comment 1

[[e-mail]]

Some further clarification of this bug from my point of view (still present in 3.5.6):

In Mac OS X, open up System Preferences > Network .
You will see a "Location" pop-up menu. Network settings can be stored in different sets for quick switching when changing location (perfect for a laptop that connects in several different networking environments).

I believe the bug is that Firefox always reads from the "Automatic" location set instead of ascertaining which location set is current and reading from that set. Users who have the proxy settings stored in that "Automatic" set should be able to use Firefox fine; however my proxy settings are stored in the "Work" location set.

If the devs are stuck, I would suggest /usr/sbin/scselect as a tool to give the current location set or altenatively /usr/sbin/networksetup to find the current active network settings.

Comment 2

[Thomas]

I can confirm this bug is accurate, we use a proxy server set by the VPN to access the internet at my workplace, setting up clients for it is a pain and we just tell them to use Safari or Internet explorer.

The bug also exists in the Windows versions of Firefox.

Comment 3

[William]

I can also confirm this to be the case. I have an OSX location set for University, and firefox ignores the proxy settings for it.

Comment 4

[Thomas]

I have spoken to someone at Mozilla, and have been told that they *are* aware of this bug... perhaps a fix in the next version.

For me, I'm still migrating customers to Chrome when they come to me over this, hope a fix is soon!

Comment 5

[posita]

It seems this is a reproducible issue.

http://support.mozilla.com/en-US/forum/1/655226
http://support.mozilla.com/en-US/forum/1/509979

I can confirm it happens to me (FF 3.6.3, OS X 10.6.4) when my location is something other than "Automatic". I have not tried it on "Automatic" however. "Manual Proxy Configuration" works fine.

Comment 6

[Steve Jobs]

I can confirm this is happening on Mac OS X 10.6.
I've never been able to get this to work.

Comment 7

[Henrik Skupin [:whimboo][⌚️UTC+1]]

This is causing us lot of trouble with our own test infrastructure now. See bug 853074. There is no way to get Firefox working with system proxy nor auto-detect settings.

For now moving to the right component so that people are aware.

Comment 8

[Steven Michaud [:smichaud] (Retired)]

Josh, is this something you'd be interested in from a networking point of view?

Comment 9

[Henrik Skupin [:whimboo][⌚️UTC+1]]

Attachment: http log

Comment 10

[Henrik Skupin [:whimboo][⌚️UTC+1]]

Probably I should not have highjacked this bug. As it turns out the problem is that automatic-proxy is always used even if it is not selected in the proxy settings. Sorry, for the noise on that bug and I will file a new one.

Reporter, does your initial setup is still causing problems? As I can see system proxies are working fine.

Comment 11

[Josh Aas]

(In reply to Steven Michaud from comment #8)
> Josh, is this something you'd be interested in from a networking point of
> view?

I'd ask Doug Turner or Patrick McManus.

Comment 12

[Henrik Skupin [:whimboo][⌚️UTC+1]]

System proxy settings are working fine on OS X. Tested with our new Mozmill CI cluster in MPT. This also applies to WPAD (auto-proxy detection).

Reporter, if you still see this problem feel free to reopen the bug. As of now this is WFM.