Open Bug 714512 Opened 13 years ago Updated 2 years ago

Internet options aren't imported as displayed, bug or works as designed?

Categories

(Firefox :: Settings UI, defect)

9 Branch
x86_64
Windows 7
defect

Tracking

()

UNCONFIRMED

People

(Reporter: John.Kitz, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:9.0.1) Gecko/20100101 Firefox/9.0.1
Build ID: 20111220165912

Steps to reproduce:

1. Performed clean install of both Windows XP and 7 on two separate systems;
2. Went to Control Panel -> Network Settings -> Internet properties -> Connections -> LAN settings on both systems;
3. Ticked "Use a proxy server for your local LAN...", configured the FQDN of the proxy and then ticked "Bypass proxy server for local addresses";
4. Proceeded to a install FF (no other apps installed yet, aside from what comes with the OS);
5. When prompted directed FF to import network settings.


Actual results:

1. In FF went to tools -> options -> advanced -> network -> settings;
2. Noticed that next to "No proxy for:" only localhost and 127.0.0.1 (which equates to localhost) are listed.


Expected results:

Expected to see localhost and/or 127.0.0.1 (as technically necessary) AND in addition, since on the LAN settings of the OS it states "Bypass proxy server for local addresses", the network to which the system is connected at the time, e.g. 10.1.1.0/24.

Should this ticket lead to a change of the code, please also consider to read the network settings of the OS every time FF starts and optionally change the settings of FF accordingly, since when I make a change to the settings after FF has been installed FF doesn't seem to detect those changes and I have to manually make the same changes to FF.
May have been caused by not configuring network exceptions through the "Advanced" button next to Proxy server field on the LAN settings tab. Will perform another install to confirm and update and/or resolve this ticket as appropriate.
Reinstalled and tried several configuration options. Connectivity problems experienced most likely caused by using wrong FQDN of proxy. However, configuration issue can't be attributed to this. Used work around for configuration issue by using automatic proxy configuration. Possible issue with importing network settings from OS remains, but may be attributable to OS.
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.