Closed Bug 630977 Opened 11 years ago Closed 11 years ago

[One Mozilla] Fix mozilla.org .htaccess redirects after merge

Categories

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

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED
Future

People

(Reporter: davidwboswell, Unassigned)

References

Details

Opening bug to track any changes needed in redirects as part of the upcoming merging of www.mozilla.com and www.mozilla.org.

Note that this involves more than just making sure existing content is redirected properly.  Both sites have a lot of crufty legacy redirects pointing back and forth to each other that will need to be fully tested.  For instance, Firefox downloads and Firefox support were both once on www.mozilla.org and there are redirects currently in place for many of those URLs.
Target Milestone: 1.5 → 1.6
Target Milestone: 1.6 → 2.0
Target Milestone: 2.0 → 2.1
Target Milestone: 2.1 → 2.2
Target Milestone: 2.2 → 2.3
Target Milestone: 2.3 → Future
Renaming to better fit the current status.

We should also test other redirects to make sure they still work.
Summary: Integrate redirects of www.mozilla.com and www.mozilla.org → Fix mozilla.org .htaccess redirects after merge
James, the redirect story on mozilla.org is a mess so I think it would make sense for the two of us to talk soon just to make sure we're covering all of the bases.

For instance, redirects are scattered across different .htaccess files, some redirects are going to go through many hops once the merge happens, redirects are continuing to change as archiving goes forward and the way redirects to the www-archive.mozilla.org many not be very clear.
Summary: Fix mozilla.org .htaccess redirects after merge → [One Mozilla] Fix mozilla.org .htaccess redirects after merge
(In reply to comment #2)
> James, the redirect story on mozilla.org is a mess so I think it would make
> sense for the two of us to talk soon just to make sure we're covering all of
> the bases.
> 
> For instance, redirects are scattered across different .htaccess files, some
> redirects are going to go through many hops once the merge happens,
> redirects are continuing to change as archiving goes forward and the way
> redirects to the www-archive.mozilla.org many not be very clear.

Let's definitely talk. I'm planning on making the mozilla.com/.org merge redirects as transparent as possible, so that everything works the way it is. I saw the www-archive redirects and other things like that, and they still work. I updated this bug to reflect the fact that in my prototype, the .htaccess redirects don't work because of a small detail (documented in http://etherpad.mozilla.com:9000/mozmerge).

We've hatched a new plan over the past couple days which entails implementing the merge redirects into Zeus, which sits in front of all of our servers. In that case, everything would run exactly the same.

That's just some context for this, but I'm definitely up for talking.
(In reply to comment #3)
> That's just some context for this, but I'm definitely up for talking.

Cool.  Unfortunately something came up at the last minute today and then the middle of this week is a work week.  I put something on your calendar for Friday.  If that doesn't work, let's try early next week.
This has been fixed. We merged the .org htaccess file into the .com one to create one holy htaccess file.

See it in action here: http://www-dev.allizom.org/
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Note that the synced htaccess file is just for staging right now, it's not the one going live. We will re-sync the htacess files before going live, see bug 673879.

This bug was more focused on *how* to merge the htaccess files, which took some figuring out.
Component: www.mozilla.org/firefox → www.mozilla.org
Component: www.mozilla.org → General
Product: Websites → www.mozilla.org
You need to log in before you can comment on or make changes to this bug.