545863 - Handle incoming support requests from special EU ballot build

Status: VERIFIED FIXED

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

Description

[David Tenser [:djst]]

The special EU ballot Firefox builds will have a slightly different app.support.baseURL so we can distinguish between the incoming traffic from that build and the normal Firefox builds (Laura to determine the new baseURL after some testing).

On the SUMO side, we need to modify .htaccess to handle these incoming requests properly. The resulting URL should have an identifier, e.g. a url parameter, so we can segment the EU ballot traffic in Omnuture.

Comment 1

[Laura Thomson :laura]

Paul, we need to define:
 a) What the baseURL should be, some kind of modification on the current value which is
app.support.baseURL = http://support.mozilla.com/1/%APP%/%VERSION%/%OS%/%LOCALE%/

b) What the URL they get redirected to looks like.  We need to add a parameter so we can distinguish these in Omniture, but at the same time make sure we don't break anything.

I'd like these worked out today, and the actual rewrite change can go into 1.5.2.  Absolute deadline is March 10, so if 1.5.2 slips we'll push just for this.

Comment 2

[David Tenser [:djst]]

Adding Ken here too. It's important that the resulting URL is distinguishable from the normal URLs. Ken: is it safe to assume that Omniture can distinguish from e.g.

http://support.mozilla.com/sv-SE/kb/Firefox+Help?style_mode=inproduct
and
http://support.mozilla.com/sv-SE/kb/Firefox+Help?style_mode=inproduct&eu
?

Comment 3

[Paul Craciunoiu [:paulc]]

Questions:
>  a) What the baseURL should be
> app.support.baseURL =
> http://support.mozilla.com/1/%APP%/%VERSION%/%OS%/%LOCALE%/
Since OS is already specified above, do we want to tie this URL to the ballot?
Something like:
http://support.mozilla.com/1/%APP%/%VERSION%/%OS%/%LOCALE%/eu
My only concern is if this name will make sense in the long run.

Laura: as for question 2 in your comment 1, david's suggestion in comment 2 seems fine, except we might want to use a value for eu, e.g. 
http://support.mozilla.com/sv-SE/kb/Firefox+Help?style_mode=inproduct&eu=1

I would like to, if possible, use the same string in the redirect as in the original url, just to make things easier.


Since we're changing the baseURL, it's implied (and I'm assuming) that we will also add rewrites for <helptopic> landings, e.g. what we currently have as:
http://support.mozilla.com/1/%APP%/%VERSION%/%OS%/%LOCALE%/pageinfo_general
... would become:
http://support.mozilla.com/1/%APP%/%VERSION%/%OS%/%LOCALE%/eu/pageinfo_general

Comment 4

[Laura Thomson :laura]

(In reply to comment #3)
> Questions:
> >  a) What the baseURL should be
> > app.support.baseURL =
> > http://support.mozilla.com/1/%APP%/%VERSION%/%OS%/%LOCALE%/
> Since OS is already specified above, do we want to tie this URL to the ballot?
> Something like:
> http://support.mozilla.com/1/%APP%/%VERSION%/%OS%/%LOCALE%/eu
> My only concern is if this name will make sense in the long run.

Sounds good.

> 
> Laura: as for question 2 in your comment 1, david's suggestion in comment 2
> seems fine, except we might want to use a value for eu, e.g. 
> http://support.mozilla.com/sv-SE/kb/Firefox+Help?style_mode=inproduct&eu=1
> 
> I would like to, if possible, use the same string in the redirect as in the
> original url, just to make things easier.
> 

Yes, so when we look back at this in a year's time we remember what it was for :)

> 
> Since we're changing the baseURL, it's implied (and I'm assuming) that we will
> also add rewrites for <helptopic> landings, e.g. what we currently have as:
> http://support.mozilla.com/1/%APP%/%VERSION%/%OS%/%LOCALE%/pageinfo_general
> ... would become:
> http://support.mozilla.com/1/%APP%/%VERSION%/%OS%/%LOCALE%/eu/pageinfo_general

Ah, what a pain.  I had overlooked this part.  But yes, you're right.

Comment 5

[Paul Craciunoiu [:paulc]]

(In reply to comment #4)
> > Since we're changing the baseURL, it's implied (and I'm assuming) that we will
> > also add rewrites for <helptopic> landings, e.g. what we currently have as:
> > http://support.mozilla.com/1/%APP%/%VERSION%/%OS%/%LOCALE%/pageinfo_general
> > ... would become:
> > http://support.mozilla.com/1/%APP%/%VERSION%/%OS%/%LOCALE%/eu/pageinfo_general
> 
> Ah, what a pain.  I had overlooked this part.  But yes, you're right.

Which pages do we want to track, exactly? Maybe instead of changing the baseURL, the Fx build could just come with the ones we want to track changed, instead. So, e.g. /firefox-help/ would instead be /eu/firefox-help/

Notably, this poses serious limitations in the future if we want to track other in-product URLs. So maybe we should just do it the above proposed way and suffer once ;)

Comment 6

[ken kovash]

(In reply to comment #2)
> Adding Ken here too. It's important that the resulting URL is distinguishable
> from the normal URLs. Ken: is it safe to assume that Omniture can distinguish
> from e.g.
> 
> http://support.mozilla.com/sv-SE/kb/Firefox+Help?style_mode=inproduct
> and
> http://support.mozilla.com/sv-SE/kb/Firefox+Help?style_mode=inproduct&eu
> ?

Do you know how you currently track a URL by what comes after the "?"?  I think we have to add a correlation within the reporting system, but I'm not totally sure.  Would it perhaps we possible to use a URL like http://support.mozilla.com/sv-SE/kb/Firefox+Help+eu?style_mode=inproduct?

Adding Blake as he might know more.

Comment 7

[Laura Thomson :laura]

(In reply to comment #6)
> (In reply to comment #2)
> > Adding Ken here too. It's important that the resulting URL is distinguishable
> > from the normal URLs. Ken: is it safe to assume that Omniture can distinguish
> > from e.g.
> > 
> > http://support.mozilla.com/sv-SE/kb/Firefox+Help?style_mode=inproduct
> > and
> > http://support.mozilla.com/sv-SE/kb/Firefox+Help?style_mode=inproduct&eu
> > ?
> 
> Do you know how you currently track a URL by what comes after the "?"?  I think
> we have to add a correlation within the reporting system, but I'm not totally
> sure.  Would it perhaps we possible to use a URL like
> http://support.mozilla.com/sv-SE/kb/Firefox+Help+eu?style_mode=inproduct?
> 

Not without a vast quantity of work so basically, no.

> Adding Blake as he might know more.

Comment 8

[[:Cww]]

(In reply to comment #6)
We set up a "campaign" or something like that in Omniture, as far as I know.

Comment 9

[Paul Craciunoiu [:paulc]]

Attachment: v1, duplicating all rewrites + /eu/ parameter

This just copies over all the current rules we have, adding a |/eu/| in the original URL and |&eu=1| in the rewritten one.

Tested on prefs, f1, help->help contents, and manually entered some of the URLs.

Comment 10

[Laura Thomson :laura]

Comment on attachment 426734 [details] [diff] [review]
v1, duplicating all rewrites + /eu/ parameter

Note: since we're changing stuff based on the baseurl, this is only going to affect inproduct links.  We will *not* be tracking people who open up their browser and type in the URL bar.  If you want that too it will need to be detected separately (will the ballot build have a different User-agent?)

Comment 11

[David Tenser [:djst]]

(In reply to comment #10)
> (From update of attachment 426734 [details] [diff] [review])
> Note: since we're changing stuff based on the baseurl, this is only going to
> affect inproduct links.  We will *not* be tracking people who open up their
> browser and type in the URL bar.  

We don't need that, so that's fine.

Comment 12

[Laura Thomson :laura]

In trunk r62396.

Comment 13

[Paul Craciunoiu [:paulc]]

(In reply to comment #12)
> In trunk r62396.
Has a bug been filed to run htaccess.sh?

Comment 14

[Stephen Donner [:stephend] Not actively reading bugmail]

(In reply to comment #13)
> (In reply to comment #12)
> > In trunk r62396.
> Has a bug been filed to run htaccess.sh?

We don't need one, iirc; staging auto-updates .htaccess on a cron?

Comment 15

[Paul Craciunoiu [:paulc]]

r62522 on branch.
(In reply to comment #14)
> staging auto-updates .htaccess on a cron?
Yes, I think you're right!

Comment 16

[Laura Thomson :laura]

We will need it in the push bug though.

Comment 17

[Vishal Kamdar [:vish_moz]]

Verified, FIXED.

Comment 18

[Stephen Donner [:stephend] Not actively reading bugmail]

We have a test for this in the testsuite, so no need for a manual test.