You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 21, 2019. It is now read-only.
_ "...An HSTS Host MUST NOT include the STS header field in HTTP responses
conveyed over non-secure transport."_
It seems that the "set_hsts_header" function should be modified to only set the header if the connection occurs over an https link. I am not 100% what the security issue is - but the standard does seem to require this. Does that seem correct to people?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Is there a problem that the STS header is also sent over an HTTP link on the first return?
See this line in para [7.2] at : http://tools.ietf.org/html/rfc6797:
_ "...An HSTS Host MUST NOT include the STS header field in HTTP responses
conveyed over non-secure transport."_
It seems that the "set_hsts_header" function should be modified to only set the header if the connection occurs over an https link. I am not 100% what the security issue is - but the standard does seem to require this. Does that seem correct to people?
The text was updated successfully, but these errors were encountered: