Closed Bug 460703 Opened 16 years ago Closed 13 years ago

first manual add-on AMO update check fails if PAC script used and if it is the very first connection from the process

Categories

(Toolkit :: Add-ons Manager, defect)

1.9.0 Branch
x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: al_9x, Unassigned)

References

Details

(Whiteboard: [closeme 2011-04-27])

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.17) Gecko/20080829 Firefox/2.0.0.17 (.NET CLR 3.5.30729) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.3) Gecko/2008092417 Firefox/3.0.3 If the following two conditions are met: 1) A proxy auto-configuration script is used. 2) The manual add-on update check is the very first http(s) connection attempt from the FF3 process then the first AMO update check will fail: An error occurred while trying to find updates for <extension or theme> The error console displays the following: Error: channel.securityInfo is null Source File: file:///<FF3 install path>/components/nsExtensionManager.js Line: 161 Checking for updates again succeeds. This is a regression from FF2. See "steps to reproduce" field. Reproducible: Always Steps to Reproduce: 1. configure FF3 to use the following PAC script: function FindProxyForURL(url, host) { return "DIRECT"; } 2. configure FF3 not to make any automatic connections on startup or when the add-ons manager is opened. Setting the homepage to blank and extensions.getAddons.showPane to false should be sufficient. Although there are other auto connections, they don't happen every time FF3 is started or at least not right away. 3. install at least one extension or theme from AMO 4. start FF3 open add-on manager and trigger the update check.
Blocks: 449216
Component: General → Add-ons Manager
Product: Firefox → Toolkit
QA Contact: general → extension.manager
Version: unspecified → 1.9.0 Branch
Al, is that still an issue in Firefox 4?
Whiteboard: [closeme 2011-04-27]
No response to requested information, closing as incomplete report.
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.