You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 6, 2022. It is now read-only.
This website allows clients to enforce HTTPS on the primary domain.
However, https://theverge.com actually redirects to http://www.theverge.com (as does http://theverge.com) and has no HSTS header set, either.
That way, typing in 'theverge.com' in your browser will never connect to the site using HTTPS in the beginning (apart from redirect caching).
Websites should always redirect to the same domain on HTTPS, where HSTS should be set. Then any other redirects can be done there. (These are also requirements for the preload list)
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently, securethenews states for 'The Verge':
However, https://theverge.com actually redirects to http://www.theverge.com (as does http://theverge.com) and has no HSTS header set, either.
That way, typing in 'theverge.com' in your browser will never connect to the site using HTTPS in the beginning (apart from redirect caching).
Websites should always redirect to the same domain on HTTPS, where HSTS should be set. Then any other redirects can be done there. (These are also requirements for the preload list)
The text was updated successfully, but these errors were encountered: