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

HTTP Strict-Transport-Security #36

Open
Mikaela opened this issue Aug 21, 2015 · 0 comments
Open

HTTP Strict-Transport-Security #36

Mikaela opened this issue Aug 21, 2015 · 0 comments

Comments

@Mikaela
Copy link
Contributor

Mikaela commented Aug 21, 2015

Currently it looks like http://ydns.eu/ does server-side redirect to https://ydns.eu/. It would be more secure if there was also HSTS so clients wouldn't even attempt to connect using http within the specified time.

I think the nginx server block would need add_header Strict-Transport-Security max-age=15552000; (for half-year).

I personally use add_header Strict-Transport-Security "max-age=15552000; includeSubdomains; preload";, but includeSubdomains wouldn't work here as it would require all users who run httpd to have HTTPS with valid certificate and preload requires subdomains to be included or the preload list doesn't accept your submission.

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

No branches or pull requests

1 participant