Skip to content
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

Increase max-age for HSTS to recommended default #34

Closed
wants to merge 1 commit into from
Closed

Increase max-age for HSTS to recommended default #34

wants to merge 1 commit into from

Conversation

wwuck
Copy link

@wwuck wwuck commented Jun 22, 2016

HSTS is now supported by all the major browsers

http://caniuse.com/#search=Strict%20Transport%20Security

@ChrisMcKee
Copy link
Member

ChrisMcKee commented Jun 23, 2016

Hi,
15768000 = 6 months; which is recommended as part of the Mozilla Security standards / generator https://mozilla.github.io/server-side-tls/ssl-config-generator/ , https://wiki.mozilla.org/Security/Server_Side_TLS#HSTS:_HTTP_Strict_Transport_Security
I
There's not really much to lose or gain increasing to 12 months; but I'll accept that the section on HSTS needs expanding to include a mention of preload + include subdomains. Subdomains was left out intentionally as at the time it was common for people to use "azure cloud services" which had a default azure domain but didn't support ssl. Setting subdomains would break all the other sites living under the main domain.

I won't merge this as I'll have to apply the change across all of the other files but i'll leave it open as a ref.

Thanks!

@ChrisMcKee ChrisMcKee closed this Jul 4, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants