1391115 - http://crash-stats.allizom.org/ (HTTP) redirects to https://crash-stats/

Status: RESOLVED FIXED

(Socorro :: Infra, task, P1)

Description

[Will Kahn-Greene [:willkg] ET needinfo? me]

There's something wrong with the redirects for the -stage environment.

STR:

1. use a browser with a fresh profile or something such that it doesn't have the correct HTTP 301 cached already

2. open the network panel in the developer tools

3. go to http://crash-stats.allizom.org/ (note the HTTP--not HTTPS)

You get an HTTP 301 to https://crash-stats/ which never resolves because it's wrong.


This bug covers figuring out what's going on.

Comment 1

[Will Kahn-Greene [:willkg] ET needinfo? me]

Miles said (and I concur--I just tested it), that going to http://crash-stats.mozilla.com/ (HTTP--not HTTPS) redirects correctly to https://crash-stats.mozilla.com/ .

Also, if you go to https://crash-stats.allizom.org/ (HTTPS), then it works fine.

I think this is a problem with the http -> https redirect. I don't know where that redirect happens, but the HTTP response suggests nginx, so maybe nginx or Django?

Miles said that when he did the -prod deploy today, the http -> https redirect for -prod stopped working. So the current theory is that the problem is on -stage and not on -prod and it's related by changes that would get deployed.

Comment 2

[Will Kahn-Greene [:willkg] ET needinfo? me]

Oops--typo in the summary. Ha!

Comment 3

[Will Kahn-Greene [:willkg] ET needinfo? me]

I looked at the configuration on the web nodes in -stage and -prod and then traced the change down to this:

https://github.com/mozilla/socorro-infra/commit/ea9428e43894eec516b7fb837280e09f4a479acf

Hope that helps!

Comment 4

[Miles Crabill [:miles]]

Reverted here: https://github.com/mozilla/socorro-infra/commit/779ccf155957a3c491a459aca29889170d3410a9.
Rebuilding stage w/ the revert, should fix this issue.

Comment 5

[Will Kahn-Greene [:willkg] ET needinfo? me]

Given comment #4, I think we're all set here. Marking as FIXED.