Closed Bug 381769 Opened 18 years ago Closed 18 years ago

Need redirect added for 2.0.0.4/1.5.0.12 rc pages

Categories

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

task
Not set
blocker

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: reed, Assigned: aravind)

Details

Please add this to www.mozilla.com: RewriteRule ^(?:\w{2,3}(?:-\w{2}(?:-mac)?)?/)?firefox/2\.0\.0\.4/(releasenotes|whatsnew)(/.*)? firefox/2\.0\.0\.4rc/$1$2 [PT] We need this for this afternoon's beta release, so please add this asap.
a=pkim
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
Checked that /2.0.0.4 redirects to /2.0.0.4rc (it does, although the pages have not been pushed to production yet). :-) What do we need to do in order to revert back this change once we ship 2.0.0.4 final? Should we just reopen this bug when it's time and back out this change or will it be better to log a new bug?
Need another rewrite added for 1.5.0.12 release notes. You have two options to pick from (only do one): RewriteRule ^firefox/releases/1\.5\.0\.12\.html$ firefox/releases/1.5.0.12rc.html [PT] Redirect temp /firefox/releases/1.5.0.12.html http://www.mozilla.com/firefox/releases/1.5.0.12rc.html
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Summary: Need redirect added for 2.0.0.4 rc pages → Need redirect added for 2.0.0.4/1.5.0.12 rc pages
Severity: critical → blocker
Assignee: server-ops → aravind
Status: REOPENED → NEW
Done. Configs synced and httpds restarted both here and at nl.
Status: NEW → RESOLVED
Closed: 18 years ago18 years ago
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.