make sure the redirects are working properly for 3.5


9 years ago
6 years ago


(Reporter: John Slater, Assigned: oremj)



Firefox Tracking Flags

(Not tracked)





9 years ago
In bug 478952 we implemented redirects for the page so Firefox 3 users would see, Firefox 2 users would see, IE users would see, etc.

With 3.5 approaching we need to update the code to accommodate the new release. 

Specifically, we need to make absolutely sure that ALL Firefox users who aren't using 3.5 (including people on 3.0, 3.5 beta, 3.5 RC, etc) see instead of /personal. If we send millions of users to a page promoting add-ons instead of the new download, that would be really really bad.

I asked Steven about this and he noticed that the current .htaccess file shows that we're just checking for Firefox 3+. Jeremy, can you make this fix to ensure that the redirects are handled properly for 3.5?
Yup; at the time when David's project was implemented, we didn't care about Shiretoko; only Firefox 3.0.x users.  Thanks for filing this.

Comment 2

9 years ago
This will just be a matter of altering the rewrite before launch. If I change it now firefox 3.0 users will see the upgrade page.

Comment 3

9 years ago
(In reply to comment #2)
> This will just be a matter of altering the rewrite before launch. If I change
> it now firefox 3.0 users will see the upgrade page.
Agreed that we wouldn't want to mess with the live version, but can you go ahead and change it on the staged version of the site? It would do a lot for my peace of mind if we had this resolved and ready to go well before launch day (whenever that ends up being). 

Steven, any thoughts on the best way to handle this?

Comment 4

9 years ago
Checking in on this bug...we really, really, really need to get it figured out before launch (which is coming soon).

Re: the issue in comment #2, can't we go ahead and change it on the staged version? Jeremy, let us know what you think.
as a reminder,  the rewrite is for the en-US locale only, people hitting should still be redirected according to the php redirect located there.

Comment 6

9 years ago
If I commit this to trunk we want be able to push any htaccess changes before launch. Is that acceptable?

Comment 7

9 years ago
(In reply to comment #6)
> If I commit this to trunk we want be able to push any htaccess changes before
> launch. Is that acceptable?
(assuming you meant won't instead of want!)

I think that's ok, but let me ask around to double check first. I'll let you know soon.
We've actually been dealing with this through the entire Firefox 3.5 RC process and the recent Thunderbird releases. What we've been doing is making changes directly on the staging tag and then pushing them live, and not altering the .htaccess file on trunk.

Sucks, but we can deal. Next time, though, we should do the 3.5 work on a branch.

Comment 9

9 years ago
Thanks Mike. Jeremy, let's proceed with the method outlined in comment #8.

And yeah, setting up a new branch from the get-go will be a must-have for next time. We can discuss that more in the post-mortem.

Comment 10

9 years ago
I'm testing this on the new production site ( and am still the /personal page when I visit with the 3.5RC.

To reiterate, we have to have this fixed before launch...we don't want Firefox 3 or 3.5beta users to see the personal page.

Jeremy, when do you think you can make the updates?

Comment 11

9 years ago
The RC shows up as 3.5, so we will give them personal. This is only going to work for 3.0 and less users.

Comment 12

9 years ago
Can we make sure that people still on the 3.5 betas see the proper download page? (not /personal)
You could use the Gecko date in the UA to match RC3 (final) exactly.

Comment 14

9 years ago
I'll defer to the experts on this for a final decision, but Reed's suggestion in comment #13 sounds good to me.

Comment 15

9 years ago
I've pushed an update. For now the behavior is:
ff 3.0 -> upgrade.html
ff 3.5 -> personal.html

Comment 16

9 years ago
After having a few offline conversations we've decided to remove personal.html from the mix altogether (at launch...will add it back in a couple of weeks).

So, the new breakdown is that ALL Firefox users, whether they're on 1.0 or 3.5, should see upgrade.html. Nobody should see personal.html.

Jeremy, thanks very much for making this edit, and let us know when you can have it made...I'd like to give WebQA a heads-up as to when they should be testing this for the last time.

Comment 17

9 years ago
I've made the change.
Last Resolved: 9 years ago
Resolution: --- → FIXED

Comment 18

9 years ago
Thanks Jeremy! Looks great to me.

FYI to all - I've filed bug 501064 to QA the redirects one final time if anyone is interested in following along there.
Component: →
Product: Websites → Websites
Component: → General
Product: Websites →
You need to log in before you can comment on or make changes to this bug.