1245699 - new activations redirection has broken socialapi

Status: RESOLVED FIXED

(Infrastructure & Operations :: IT-Managed Tools, task)

Description

[Shane Caraveo (:mixedpuppy)]

I was just testing something unrelated and noticed that activations.cdn.mozilla.net now redirects to activations-origin.cdn.mozilla.net.  SocialAPI activations are tied to a pre configured domain in firefox, which currently only includes "https://activations.cdn.mozilla.net".  Landing the user on any other domain breaks the activation routine.  We need to turn off the redirection to activations-origin.

Comment 1

[Ryan C [:ryanc] (UTC-4)]

Lowering this to normal to stop paging sysadmins.

Atoll is aware of this and is looking into it.

Comment 2

[Jake Maul [:jakem]]

This is fixed, with coordination in IRC.

This happened when we moved from Edgecast to AWS Cloudfront for CDN properties (late January... this one on Jan 28).

Edgecast was configured to send a different Host: header when connecting to the origin servers - specifically, it would pass through the one the user originally requested rather than use the origin server hostname.

AWS Cloudfront, however, was doing the opposite- using the origin's hostname rather than the Host header from the end user.

The net effect is that the behavior is slightly different on the origin- any time the origin issues a local redirect (for example, for adding "/en-US/" to the path) it would be handled using the Host header that the origin saw. AWS CF would then pass that redirect through to the end user, rather than translating it back to the original Host header the user requested.


There are multiple ways to handle this, but the simplest, cleanest way is to have CF pass through the original Host header requested by the end user, as Edgecast was doing. This is what we've done.