Dan Callahan

At a high level, Portier just wants a workflow that looks like: 1. User types an identifier into the site 2. Portier verifies the user's control over that identifier 3....

Here's what our Travis CI scripts do, and roughly how long each step takes: ``` # Build and boot containers 5:17 | VERSION=latest make build-base :58 | VERSION=latest make build-kuma...

And what's taking so much time in our docker build? I ran a build locally with an empty cache and got the following timings for each step in our Dockerfile:...

Hm. So looking at that Sentry report, starting in the middle of the traceback I see: Passing the same arguments locally in a `./manage.py shell` session, I can successfully reverse...

Yeah, it's the Host header. See: ``` $ curl -I -H "Host: demos-origin.mdn.mozit.cloud" \ "https://demos-origin.mdn.mozit.cloud/en-US/docs/en-US/docs/Web/API/WebGL_API/By_example/Canvas_size_and_WebGL$samples/canvas-size-and-webgl-source?revision=1588345" HTTP/1.1 404 Not Found Cache-Control: max-age=0, no-cache, no-store, must-revalidate Content-Length: 11123 Date: Tue, 03 Mar...

Ah, crap. Maybe I broke it here? https://github.com/mdn/kuma/commit/9a89d2dd3377c52ca407f3c56e89cdc2defc649a?diff=split

Or potentially here? https://github.com/mdn/kuma/commit/ce6f64fb02860ec1d00044ef682277f7b57a7fa0?diff=unified I don't think I've done anything else to touch the redirects.

Yeah. It does seem to have coincided with the Django 2 deploy...

Or maybe not? We have over 2,100 instances of this error at https://sentry.prod.mozaws.net/operations/mdn-prod/issues/7259753, and which was first seen on February 12th.

Oh, this is _old_. Here are another 8,100 events for that same URL, first seen back on November 13th, 2019: https://sentry.prod.mozaws.net/operations/mdn-prod/issues/6659001/?query=url:%22https://demos-origin.mdn.mozit.cloud/en-US/docs/en-US/docs/Web/API/WebGL_API/By_example/Canvas_size_and_WebGL$samples/canvas-size-and-webgl-source%22