407825 - redirect firefox 3 beta 2 release candidate http requests to devnews

Status: VERIFIED FIXED

(mozilla.org Graveyard :: Server Operations, task)

Description

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

The URLs:

http://stage.mozilla.org/pub/mozilla.org/firefox/nightly/3.0b2-candidates/*
and
http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/3.0b2-candidates/*

should be redirected to

http://developer.mozilla.org/devnews/index.php/2007/12/10/firefox-3-beta-2-expected-in-late-december/

in order to keep the Diggers from linking to the wrong place.

Comment 1

[Aravind Gottipati [:aravind]]

Done.

Comment 2

[Robert Helmer [:rhelmer]]

This is going to cause the updates generation step to break.

Can we allow direct HTTP access to http://stage.mozilla.org/pub/mozilla.org/firefox/nightly/3.0b2-candidates/rc1/ from the build network?

If not, then we need to get started testing a workaround, so please let us know soon :)

Comment 3

[Dave Miller [:justdave]]

use the ftp link via ftp and it works

Comment 4

[Robert Helmer [:rhelmer]]

(In reply to comment #3)
> use the ftp link via ftp and it works

Yeah, I was thinking of using this fact if we need to workaround.

The updates generation stuff is all hardcoded to use the same URL for testing updates as it uses for generating the updates.

We can change this, but probably not by tomorrow. So either we can workaround it on the server side by allowing this, or build can workaround by manually intervening and generating updates using FTP as source, then reconfigure and set up AUS.

The latter probably adds a couple hours of build and test work to the release, not sure about the former (which is why I'm asking if we can do that instead :)).

Comment 5

[Robert Helmer [:rhelmer]]

Actually, now that I think about it, this makes it impossible for QA to test updates as well, so it's a bigger deal than I have made it out to be so far.

Can we just turn off the redirect for .mar (update) files, for all incoming requests? That'd fix both QA and build's problem.

Comment 6

[Aravind Gottipati [:aravind]]

Just so I am clear, you want me to allow access to *.mar files on both stage and ftp?

And only to the mar files in the rc1 directory?

Comment 7

[Robert Helmer [:rhelmer]]

(In reply to comment #6)
> Just so I am clear, you want me to allow access to *.mar files on both stage
> and ftp?

Right.

> And only to the mar files in the rc1 directory?

Actually all of 3.0b2/ would be better, in case we do multiple RCs.

Comment 8

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

Right now the redirect is resulting in an error:

going to:

http://stage.mozilla.org/pub/mozilla.org/firefox/nightly/3.0b2-candidates/rc1/

redirects to:

http://developer.mozilla.org/devnews/index.php/2007/12/10/firefox-3-beta-2-expected-in-late-december/rc1/

which is 404 (the /rc1 bit shouldn't be there)

Comment 9

[Aravind Gottipati [:aravind]]

Okay, please try it now.  Thanks to justdave for fixing this.

Now /rc1/ at the end shouldn't be carried over.

*.mar files should be served correctly.

Comment 10

[[e-mail] (:bhearsum)]

Just tried this link: http://stage.mozilla.org/pub/mozilla.org/firefox/nightly/3.0b2-candidates/rc1/firefox-3.0b2.be.mac.complete.mar

It served me the mar fine.