304432 - Attempting http://www.mozilla.org/update/ gives " 403: Access Forbidden "

Status: VERIFIED DUPLICATE of bug 301321

(Firefox :: General, defect)

Description

[Kris Silver]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b3) Gecko/20050712 Firefox/1.0+
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b3) Gecko/20050712 Firefox/1.0+

On Deer Park Alpha 2, clicked HELP > Check for updates.  Get "AUS: Update XML
File not found".  I know auto update is turned off (?) but this should surely
update extensions, or check for manual upgrades for Deer Park Alpha 2 or
something.  

It says check manually at http://www.mozilla.org/update/ but clicking that link
and trying it within the browser gives "403: Access Forbidden" well why link
user to this then?

Also, clicking this link in the pop up box opens this error page in a new
window.  All settings in options are set to use tabs not windows:

Open Links it other applications - in new tabs
Force Links that open in new windows to open in - a new tab

Reproducible: Always

Steps to Reproduce:
1. HELP > Check for updates
2. Click link to manual update
3. New window opened (not tab) and "403: Acess forbidden".

Actual Results:  
1. "AUS: Update XML File not found"
2. New window instead of tab opened
3. 403: Access Forbidden

Expected Results:  
1. Updated extensions, and/or Deer Park
2. If not specify a manual update that is available
3. Open the basic update link in a new tab
4. Allow to see and download update, or advise if there isn't one

Comment 1

[Dave Townsend [:mossop]]

*** This bug has been marked as a duplicate of 301321 ***

Comment 2

[Kris Silver]

My bad sorry, didn't search well enough.  I agree with most on this, for the
time being there is littler point telling user to update manually at this site,
if it is just an error page.  At least make it a valid page to manually upgrade
until auto upgrade is turned on.

Also, The area of this bug with regards to windows being opened instead of tabs
has not been responded to.  This also applies to clicking visit home for an
extension in the extensions manager, windows instead of tabs despite setting
otherwise.  Can someone please comment on this.  If needs by I'll submite a new
bug, again I can't find one already.

Comment 3

[Dave Townsend [:mossop]]

Comments on the error page should be put into bug 301321, just remember though
that this is an alpha product we are testing here, minor things like this will
be fixed by the time the majority of users get their hands on it.

For the window/tab issues I'd file another bug with that as the summary, but you
may want to take a look at bug 262575 which is a very similar situation and
would probably fix this issue.