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

Add a warning if HTTP->HTTPS redirects are not permanent (301/308) #93

Open
lgarron opened this issue Jan 13, 2017 · 1 comment
Open

Comments

@lgarron
Copy link
Collaborator

lgarron commented Jan 13, 2017

Or maybe an error?

@ivanr's Hardenize checks for this.

@ivanr
Copy link

ivanr commented Jan 14, 2017

When I added the check I thought that having a permanent redirection is a preloading requirement. Looking at the web site right now, that doesn't seem to be the case. So my message will need to be toned down to promote permanent redirection as HSTS best policy only.

That said, I think there's some value in requiring permanent redirects for consistency with the RFC and as a small barrier to prevent preloading by mistake.

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

2 participants