Closed
Bug 192540
Opened 22 years ago
Closed 21 years ago
PAC: is not loaded during the first launch until you manually reload it in preferences
Categories
(Core :: Networking, defect)
Tracking
()
VERIFIED
WORKSFORME
People
(Reporter: wlb.bag, Assigned: dougt)
Details
Attachments
(1 file)
40.64 KB,
text/plain
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de-AT; rv:1.2.1) Gecko/20021130
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; de-AT; rv:1.2.1) Gecko/20021130
A freshly installed mozilla (pre-configured to use a proxy.pac file) the
proxy.pac file is not loaded until the user manually reloads it in 'preferences'.
Reproducible: Always
Steps to Reproduce:
1. install mozilla using a pre-configured language pack instructing mozilla to
use a proxy.pac file.
2. load any site
Actual Results:
browser gets a timeout
Expected Results:
load proxy.pac, do the request according to the settings.
Can you describe the method of pre-configuration?
QA Contact: benc → pacqa
Summary: proxy.pac is not loaded during the first launch until you manually reload it in preferences → PAC: is not loaded during the first launch until you manually reload it in preferences
options concerning the PAC (all.js is attached as well) :
---------------8<------------------------------------------
pref("network.proxy.autoconfig_url",
"http://shai-hulud.wlb.sin/proxy.pac.php");
//pref("network.proxy.type", 0);
// Typ des Proxy-Servers:
// 0 Kein Proxy (direkte Verbindung zum Internet)
// 1 Manuelle Proxy-Konfiguration
// 2 Automatische Proxy-Konfiguration
pref("network.proxy.type", 2);
---------------------------------------------->8-----------
customization is done by editing browser.xpi:/bin/defaults/pref/*.js and
rezipping browser.xpi
Comment 3•21 years ago
|
||
Reporter: Is this still a problem with a current Mozilla build?
Comment 4•21 years ago
|
||
no response-->resolving wfm
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → WORKSFORME
VERIFIED:
There are some reports of PAC getting lost in cache, but we need more info to
keep the bug open.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•