1352267 - sso.mozilla.com uses uncached 301s

Status: RESOLVED FIXED

(Infrastructure & Operations :: SSO: Issues, task)

Description

[:Atoll]

Today, sso.mozilla redirects using:

RewriteRule ^/place https://mozilla.okta.com/home/mozillacorp_place_1 [R=301,NC,L]

301 will be cached for some random period of time that each browser decides independently. We should specify a Cache-Control header on all 301 redirects that ensures a good user experience.

Typically, on a redirect-only virtual server in Webops, we would do:

Header always set Cache-Control "max-age=60"

for 60 seconds, or =300 seconds, or whatever is best. This helps guide not only clients but also caching load balancers (Zeus, today, and AWS CloudFront/ALB tomorrow) to behave reproducibly.

This is not urgent to fix, but should be taken under review as part of the upcoming AWS deployment. You are welcome to resolve this bug whenever you've reviewed it, whether or not action results. Cheers!

Comment 1

[Andrew Krug [:andrew]]

Reviewed and planned for future enhancement to the redirect feature.  Thanks.