-
Notifications
You must be signed in to change notification settings - Fork 92
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is a 302 redirect honored? #198
Comments
The header has to be sent on the response to Depending on your server software, there may be a separate settings to do this for redirects. For example, in Apache you have to use the
|
thanks @lgarron, @shaunwarman you can close this @lgarron it might be good to make a note in the landing page that "if you 302 redirect to i18n landing pages like /en, note that your 302 redirect needs the HSTS header present" - not sure if many others have this but would be good to dummy-proof (since other sites follow their redirects on HSTS tests, and hstspreload.org does not). |
I think mentioning i18n is a bit too specific. The Deployment Recommendations mentions adding the Strict-Transport-Security header to all HTTPS responses. Would it help to clarify that by adding "including redirects"? |
that'd be great |
Trying https://fowardemail.net there is a 302 redirect to
https://forwardemail.net/<locale>
(e.g. https://forwardemail.net/en) where hsts header is presenthstspreload.org responds with
Error: No HSTS header Response error: No HSTS header is present on the response.
Does the missing hsts header on the initial response and 302 redirect to where hsts header is present cause the issue?
I can see http -> https redirect via 301.
Using competitors like https://gf.dev/hsts-test says things are good.
The text was updated successfully, but these errors were encountered: