279064 - Add addons.mozilla.org to whitelist

Status: RESOLVED WORKSFORME

(Firefox :: Settings UI, defect)

Description

[alanjstr]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

UMO is moving to AMO.  To ease this transition, we currently redirect to
A.U.M.O.   This wastes server resources.  Requesting blocking 1.0.1 and 1.1. 

Reproducible: Always

Steps to Reproduce:

Comment 1

[Wolf [:wolf]]

My original understanding was the by myk added addons.mozilla.org to the
whitelist as part of the UMO breakup bug. (the # escapes me.)

CC'ing myk for comment.

Comment 2

[Wolf [:wolf]]

Bug 271473, Attachment 168738 [details] [diff]...

-pref("xpinstall.whitelist.add", "update.mozilla.org");
+pref("xpinstall.whitelist.add", "update.mozilla.org,addons.mozilla.org");

looks like this is already done, though I don't have a nightly build to verify.

Comment 3

[Myk Melez [:myk] [@mykmelez]]

> UMO is moving to AMO.  To ease this transition, we currently redirect to
> A.U.M.O.   This wastes server resources.

Redirecting to aumo is necessary now and for the foreseeable future because
Firefox 1.0 users can't install from amo.  The redirect from umo to aumo should
*not* be removed, although we can redirect to amo for users we know can install
from amo, which is currently only users of recent nightly builds and the next
regular version of Firefox, whenever that gets released.

Comment 4

[alanjstr]

What I meant was, I know 1.0.1 is coming out soon.  Why not update their
whitelist too.

Comment 5

[Mike Connor [:mconnor]]

sorry for bugspam, long-overdue mass reassign of ancient QA contact bugs,
filter on "beltznerLovesGoats" to get rid of this mass change