Closed Bug 319856 Opened 19 years ago Closed 19 years ago

lockPref of autoconfig_url causes it to be loaded twice

Categories

(SeaMonkey :: General, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: pe1chl, Unassigned)

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8b4) Gecko/20050913 SeaMonkey/1.0a
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; nl-NL; rv:1.7.11) Gecko/20050728

I have created a mozilla.cfg file to lock some settings to fixed values appropriate to our company,
Amongst them is a lockPref for network.proxy.autoconfig_url that sets a URL for a proxy autoconfig script.

Now that this value is locked, the URL is loaded twice (very quickly) when starting Mozilla.
Before, when setting the autoconfig_url manually, it was loaded only once.

Reproducible: Always

Steps to Reproduce:
1. setup a locked configuration environment
2. add network.proxy.autoconfig_url setting
3. start mozilla and watch the traffic or the webserver log

Actual Results:  
Script is loaded twice from the server.
Our script is generated using a cgi-bin, and it is run twice.

Expected Results:  
Script should be loaded once.
wfm here with a current trunk build on win2k, it only loads the pac file once from the web server (i used a static PAC file to test this, but i think it should not matter if it gets a static PAC file or some output from a CGI script). Have you tried if you also see this bug with a SeaMonkey nightly (or SeaMonkey 1.0a if you want to)?
I have just tested an install of SeaMonkey 1.0a and indeed it works OK there.

Hopefully a stable release based on SeyMonkey will be available soon, as this also fixes other pending problems for us.
(I cannot rollout an alpha/beta version with Debug and QA menus)
I think a final SeaMonkey 1.0 release can be expected in January or February (or so is the roadmap at least).
so this is wfm then.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.