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.

Sign up for GitHub

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

Jump to bottom

consider hsts #613

Closed

mcmanus opened this issue May 7, 2018 · 0 comments

Labels

Contributor

mcmanus commented May 7, 2018

section 4.3.2

HTTP-specific features such as cookies [RFC6265], authentication [RFC7235], caching [RFC7234], and CORS [FETCH] might or might not work correctly, depending on how they are defined and implemented. Generally, they are designed and implemented with an assumption that the URL will always be “http” or “https”.

likely worth working HSTS into that list.. we've seen it fail to provide its security benefit when mixed on hosts that provide ftp resources

mcmanus added the bcp56bis label

mnot closed this as completed in

3e2354c

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment