This repository has been archived by the owner on Jun 20, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 4
Force TLS connections? #10
Comments
What happens if we don't? What happens after a year? |
If we don't we get this somewhat weird bouncing of people going to "Warning! Once you force TLS connections, people who visit your site won’t be able to access the HTTP version if you change this setting later." I'm guessing that means the process is somewhat irreversible for a year. |
OK. I'm happy to force TLS. |
@btracey I think force TLS is the way to go. Netlify plans to support exclusively TLS traffic if they haven't done so already. See this issue from the netlify team: netlify/cli#158 |
This is done with the new website build. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Netlify has a "Force TLS connections" , "Forcing TLS will redirect all traffic to HTTPS and set Strict Transport Security Headers for 1 year."
Is this something we want? We somewhat force this anyway because the hugo generation (at least at the moment) hard paths https links.
The text was updated successfully, but these errors were encountered: