Firefox sites send 3.6 beta users to Upgrade page

VERIFIED FIXED in 3.6

Status

www.mozilla.org
General
--
blocker
VERIFIED FIXED
9 years ago
6 years ago

People

(Reporter: fligtar, Unassigned)

Tracking

unspecified

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

9 years ago
Prior to using the 3.6 beta, when going to a "Firefox website" like firefox.com, getfirefox.com, firefoxaddons.com, etc. I would be taken to the Get Personal page as I was an existing Firefox user.

Using the 3.6 beta, I am taken to the "upgrade to 3.5 page", which makes me think we are checking for specific versions when determining what landing page to redirect to.

If we can't use version ranges (everything < 3.5 gets upgrade, everything >= gets Get Personal), we should add some 3.6 beta versions to the redirector as a good number of people will be using them.
Target Milestone: --- → 3.6
This redirecting is controlled in .htaccess and does appear to be 3.5-specific.

# firefox landing pages A/B test (bug 478952)
# Firefox 3.5
RewriteCond %{REQUEST_URI} ^/en-US(?:/projects)?/firefox(?:/(?:index.html)?)?$
RewriteCond %{HTTP_USER_AGENT} ^.*Firefox/3.5.*$
RewriteRule . /en-US/firefox/personal.html [R=temp,L]
# Firefox 3 and less
RewriteCond %{REQUEST_URI} ^/en-US(?:/projects)?/firefox(?:/(?:index.html)?)?$
RewriteCond %{HTTP_USER_AGENT} ^.*Firefox/.*$
RewriteRule . /en-US/firefox/upgrade.html [R=temp,L]
# MSIE
RewriteCond %{REQUEST_URI} ^/en-US(?:/projects)?/firefox(?:/(?:index.html)?)?$
RewriteCond %{HTTP_USER_AGENT} MSIE
RewriteCond %{HTTP_USER_AGENT} !Opera
RewriteRule . /en-US/firefox/ie.html [R=temp,L]
# everybody else: regular page
RewriteCond %{REQUEST_URI} ^/en-US(?:/projects)?/firefox(?:/(?:index.html)?)?$
RewriteRule . /en-US/firefox/firefox.html [R=temp,L]


We'll need some guidance on how these redirects should work for 3.6 (and 3.5 if those will change).

Comment 2

9 years ago
Good catch. For now, users of both 3.5 and the 3.6 beta should see the http://en-us.www.mozilla.com/en-US/firefox/personal.html page.

Once 3.6 launches, only people using the GA version of 3.6 should go to http://en-us.www.mozilla.com/en-US/firefox/personal.html. People using any other version of Firefox should go to https://www.mozilla.com/en-US/firefox/upgrade.html.

Let me know if that makes sense, or if further clarification is needed. And this needs to be assigned to someone in IT, right?
(In reply to comment #2)

> Let me know if that makes sense, or if further clarification is needed. And
> this needs to be assigned to someone in IT, right?

Typically, webdev makes changes to .htaccess, and IT just pushes them, iirc.

Comment 4

9 years ago
(In reply to comment #3)
> (In reply to comment #2)
> 
> > Let me know if that makes sense, or if further clarification is needed. And
> > this needs to be assigned to someone in IT, right?
> 
> Typically, webdev makes changes to .htaccess, and IT just pushes them, iirc.

Hey Mike. Who would you recommend for this project? Fixing it for the beta is important, but fixing it for the GA is essential...ideally we could get one fix to take care of both. 

Thanks!

Comment 5

9 years ago
(In reply to comment #4)
> (In reply to comment #3)
> > (In reply to comment #2)
> > 
> > > Let me know if that makes sense, or if further clarification is needed. And
> > > this needs to be assigned to someone in IT, right?
> > 
> > Typically, webdev makes changes to .htaccess, and IT just pushes them, iirc.
> 
> Hey Mike. Who would you recommend for this project? Fixing it for the beta is
> important, but fixing it for the GA is essential...ideally we could get one fix
> to take care of both. 

Morgamic...ping. How should we proceed here? This has relevance for both pre-3.6 testing and the launch itself.
Severity: normal → blocker
Ok, I warn you, I'm bad at rewrites and regexps, but I think the change in r57213 (trunk only) does what you want.  Check it out.
Tested with...

FF 3.5 -> personal
FF 3.6 -> personal
FF 3.0 -> upgrade
Safari -> firefox

... on trunk.

Btw, this doesn't fix the case of sending 3.5 users to upgrade.html when 3.6 is released as GA.  I think you were getting at that in comments 2 and 4, but I think that's not possible until 3.6 is GA, right?  I could be wrong.

Comment 8

9 years ago
Looking good to me, thanks Alex. I'll resolve, and will let QA confirm.

> Btw, this doesn't fix the case of sending 3.5 users to upgrade.html when 3.6 is
> released as GA.  I think you were getting at that in comments 2 and 4, but I
> think that's not possible until 3.6 is GA, right?  I could be wrong.

Yep, that's what I was talking about in comments #2 and 4. Stephen Donner, if I'm remembering correctly does it take an IT bug to make that fix?
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → FIXED
My patch was pushed live this morning, looks good to me.
Verified FIXED; Namoroka goes to /upgrade.html, but I don't think we care.
Status: RESOLVED → VERIFIED
(Assignee)

Updated

6 years ago
Component: www.mozilla.org/firefox → www.mozilla.org
Product: Websites → Websites
(Assignee)

Updated

6 years ago
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.