Skip to content
This repository has been archived by the owner on Jan 6, 2022. It is now read-only.

About redirects and www subdomains #144

Open
jomo opened this issue Nov 28, 2017 · 0 comments
Open

About redirects and www subdomains #144

jomo opened this issue Nov 28, 2017 · 0 comments

Comments

@jomo
Copy link

jomo commented Nov 28, 2017

Currently, securethenews states for 'The Verge':

  • The default for this website is secure.
  • 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)

screenshot

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant