318717 - [404] http://www.mozilla.com/firefox/upgrade (addons.mozilla.org sends you here if you have e.g. Firefox 1.0.2)

Status: RESOLVED FIXED

(www.mozilla.org :: General, defect)

Description

[Jan Mattila]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051111 Firefox/1.5
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051111 Firefox/1.5

The page http://www.mozilla.com/firefox/upgrade does not exist. This probably would not be a problem otherwise, but with fx 1.0.7 (Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915 Firefox/1.0.7), when trying to connect to the https://addons.mozilla.org site, you get redirected to the aforementioned URL, which does not exist.

Reproducible: Always

Steps to Reproduce:
1. open https://addons.mozilla.org with fx 1.0.7 

or

1. open http://www.mozilla.com/firefox/upgrade

Actual Results:  
Not Found

The requested URL /firefox/upgrade/ was not found on this server.

Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.
Apache/2.0.52 (Red Hat) Server at www.mozilla.com Port 80

Expected Results:  
An upgrade page that does exist? It's a good enough (though debatable) idea to make people upgrade their browsers to get addons, but redirecting to a 404 is probably not the best way go about this.

I'm sorry if this bug was filed in the wrong container. I tried to find out the right place for mozilla.com website feedback, and this was the closest I could figure out.

Comment 1

[Jan Mattila]

Not reproducible with the en-GB 1.0.7 build for Linux (Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.7.12) Gecko/20050920 Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.7.12) Gecko/20050920 Firefox/1.0.7) downloaded from http://www.mozilla.com/products/download.html?product=firefox-1.0.7&os=linux&lang=en-GB, although it does take a _long_ time to load the https://addons.mozilla.org main page.

Comment 2

[Jan Mattila]

Sorry, copypaste bug... the correct version string for the Linux 1.0.7. is obviously:

Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.7.12) Gecko/20050920 Firefox/1.0.7

I am a middle-button copypaste n00b.

Comment 3

[Jesse Ruderman]

If I fake my UA to say Firefox 1.0.2 using http://web-sniffer.net/, https://addons.mozilla.org/ redirects me to http://www.mozilla.org/products/firefox/upgrade/, which redirects to http://www.mozilla.com/firefox/upgrade/, which is a 404.  This doesn't happen with a Firefox 1.0.7 UA.

Comment 4

[Mike Beltzner [:beltzner, not reading bugmail]]

Known issue, will be fixed shortly. Browsers <= 1.0.4 had a vulnerability where malicious code could be installed through bouncing off the amo servers and thus getting past the whitelist. Or something like that. All I know is that we've got Steven looking into posting the new page.

Comment 5

[Steven Garrity [:sgarrity]]

Fixed: http://www.mozilla.com/firefox/upgrade

Comment 6

[Steven Garrity [:sgarrity]]

It seems that addons.mozilla.org first redirects to http://www.mozilla.org/products/firefox/upgrade/ which should then redirect to mozilla.com/firefox/upgrade/ - but it doesn't.

Either the .org upgrade page has to be setup to redirect to the .com page, or the addons.mozilla.org script should redirect directly to the .com

Reopening.

Comment 7

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

Redirect set up from .org -> .com.

Comment 8

[Dave Miller [:justdave]]

Reopening... the redirect from addons is still dead.
http://www.mozilla.org/products/firefox/upgrade/ still gets a 404.

Comment 9

[Reed Loden [:reed]]

*** Bug 322031 has been marked as a duplicate of this bug. ***

Comment 10

[Dave Miller [:justdave]]

I've fixed the redirect on addons to point directly to the page on mozilla.com

That should put this to bed until the next time someone redoes the site. ;)

Comment 11

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

Yeah, the problem with what I did in comment 7 is that redirecting upgrade/index.html only works as long as the directory upgrade exists, and it got wiped out in the nightly rebuild.  I thought it was necessary to get the slash dropped, but it's not.  The redirect is fixed now.