Redirect to seamonkey and thunderbird apps via user agent

[kumar303]

Describe the problem and steps to reproduce it:

• Set your user agent to that of seamonkey or thunderbird
• Load a page without an app, such as https://addons-dev.allizom.org/en-US/

What happened?

You are redirected to https://addons-dev.allizom.org/en-US/firefox/

What did you expect to happen?

• For a seamonkey user agent you should be redirected to https://addons-dev.allizom.org/en-US/seamonkey/
• For a thunderbird user agent you should be redirected to https://addons-dev.allizom.org/en-US/thunderbird/

Anything else we should know?

• seamonkey and thunderbird URLs are still served from the legacy site: https://github.com/mozilla/addons/issues/11066
• As of https://github.com/mozilla/addons/issues/11043 the addons-frontend server will need to be in charge of redirects

[muffinresearch]

Duplicate of https://github.com/mozilla/addons/issues/11066

[muffinresearch]

@kumar303 not sure if this is at cross purposes with mozilla/addons#11066? That issue was about making sure SeaMonkey and Thunderbird UAs only ever see the legacy site at the nginx level not just based on paths - path handling was already in place also at the nginx level.

Let me know if I've misunderstood anything.

[kumar303]

@muffinresearch I'm confused. The STR up above on dev lands me https://addons-dev.allizom.org/en-US/firefox/ but it should land me at https://addons-dev.allizom.org/en-US/thunderbird/ (or seamonkey). With my patch it will do so.

[muffinresearch]

We talked about this on irc, the confusion was caused by kumar's UA extension not setting the test UA correctly.

[kumar303]

Yeah, I was experiencing some kind of bug where the UA was not getting applied to the request.

The clarification I was missing is that nginx will inspect the user agent. It always serves the legacy site to seamonkey/thunderbird UAs and the legacy site does redirects as expected.