Closed Bug 745479 Opened 13 years ago Closed 11 years ago

Addons not hosted by AMO still ping for metadata

Categories

(Toolkit :: Add-ons Manager, defect)

10 Branch
x86
Linux
defect
Not set
normal

Tracking

()

RESOLVED WONTFIX

People

(Reporter: mozilla, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Linux i686; rv:10.0.1) Gecko/20100101 Firefox/10.0.1 Build ID: 20120208060813 Steps to reproduce: 1. Create an addon including the updateURL element to indicate that the addon is not hosted at addons.mozilla.org. 2. Install the addon using ctrl-O. Actual results: Firefox submitted a search to AMO trying to populate the addon manager cache. This fails of course. This continues to happen since there is never a cache entry when Firefox looks so it always goes to mozilla.org to look for the metadata. Expected results: Nothing? Or is it possible to get metadata at updateURL? I don't think so.
Component: Untriaged → Add-ons Manager
Product: Firefox → Toolkit
QA Contact: untriaged → add-ons.manager
We originally implemented this because the plan was to allow anyone to upload their add-on information to AMO yet still host their add-on elsewhere. That got abandoned later so not sure what we want to do with this now.
It is hardly a critical problem. I only spotted it because of the delay that it introduces when loading a non-AMO addon, which of course is never in the addon cache so always causes a lookup.
This is intentional, because we want AMO to be able to override add-on metadata in the case of add-ons that cause stability problems, even when that add-on is not hosted at AMO.
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.