-
Notifications
You must be signed in to change notification settings - Fork 411
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
HSTS Support #151
Closed
Closed
HSTS Support #151
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
In addition of the HTTPS redirect, adding HSTS support will even skip this redirect the next time a supporting browser asks for a non-secured resource. We potentially gain an HTTP query per non-HTTPS requested resource and smoothly increased security and privacy. The value is set accordingly to the recommended value in the spec. If you agree with this proposal, the same change can be propagated in other boilerplate files (like Nginx etc.).
@oncletom can you amend the commit and:
Thanks :) |
Oh gosh, I did not even realize it was living one line below :-( I'll do, thanks :-) |
`includeSubDomains` is part of the recommended value in the original spec of HSTS.
I've updated the commit and also added a precision about |
alrra
pushed a commit
that referenced
this pull request
May 29, 2013
The `includeSubDomains` optional directive allows the user to apply the `HTTP Strict Transport Security` rule to all of the site's subdomains: * http://tools.ietf.org/html/draft-ietf-websec-strict-transport-sec-14#section-6.1 * https://developer.mozilla.org/en-US/docs/Security/HTTP_Strict_Transport_Security Ref: #151
alrra
pushed a commit
that referenced
this pull request
May 29, 2013
The `includeSubDomains` optional directive allows the user to apply the `HTTP Strict Transport Security` rule to all of the site's subdomains: * http://tools.ietf.org/html/draft-ietf-websec-strict-transport-sec-14#section-6.1 * https://developer.mozilla.org/en-US/docs/Security/HTTP_Strict_Transport_Security Ref: #151
alrra
pushed a commit
that referenced
this pull request
Jun 27, 2013
The `includeSubDomains` optional directive allows the user to apply the `HTTP Strict Transport Security` rule to all of the site's subdomains: * http://tools.ietf.org/html/draft-ietf-websec-strict-transport-sec-14#section-6.1 * https://developer.mozilla.org/en-US/docs/Security/HTTP_Strict_Transport_Security Ref: #151
alrra
pushed a commit
to h5bp/server-configs-apache
that referenced
this pull request
Jul 26, 2013
The `includeSubDomains` optional directive allows the user to apply the `HTTP Strict Transport Security` rule to all of the site's subdomains: * http://tools.ietf.org/html/draft-ietf-websec-strict-transport-sec-14#section-6.1 * https://developer.mozilla.org/en-US/docs/Security/HTTP_Strict_Transport_Security Ref: h5bp/server-configs#151
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In addition of the HTTPS redirect, adding HSTS support will even skip this redirect the next time a supporting browser asks for a non-secured resource.
We potentially gain an HTTP query per non-HTTPS requested resource and smoothly increased security and privacy.
The value is set accordingly to the recommended value in the spec.
If you agree with this proposal, the same change can be propagated in other boilerplate files (like Nginx etc.).
It's a follow-up of h5bp/html5-boilerplate#1365.