Closed
Bug 367014
Opened 18 years ago
Closed 18 years ago
Updating extension fail because proxy not authenticated on startup
Categories
(Toolkit :: Add-ons Manager, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 312473
People
(Reporter: paolo.marani, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; it; rv:1.8.1.1) Gecko/20061204 Firefox/2.0.0.1 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; it; rv:1.8.1.1) Gecko/20061204 Firefox/2.0.0.1 If the computer runs under squid-proxy (possibly other proxies too) the update extension manager does not properly work (download fail). The server is contacted, then the user is presented with the list of available extension update (IETab in my case, but does not matter). If i choose Download and install extension now" there is an authentication failure and the download fail. If i continue and i connect to ANY web page, a message box appear asking me for credentials. Once entered required credentials i can now surf the web. Returning to the extension manager, this time it will SUCCEED downloading the updated extension (proxy already authenticated). I would like the proxy authentication box to appear also when updating extensions at startup. Reproducible: Always Steps to Reproduce: 1. FF2 ready to download an updated extension at startup 2. The extension download fails (proxy authentication failure) 3. The user authencicate normally on first page load 4. Retrying to download the extension it works Actual Results: Proxy auth not asked when the first browser operation is to download an update Expected Results: FF2 should ask for proxy auth everywhere is required! Both extensions and themes are affected, when under squid-proxy, trying to update at startup without asking authorization make that feature useless. Would be nice to add an hidden setting to AUTOMATE the send proxy credentials.
Updated•18 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → DUPLICATE
Assignee | ||
Updated•16 years ago
|
Product: Firefox → Toolkit
You need to log in
before you can comment on or make changes to this bug.
Description
•