问题原文
原帖链接 · Kevin Burke · CC BY-SA 3.0
I'd like to submit my personal site into the Chrome HSTS preload list.
The site there says:
In order to be included on the HSTS preload list, your site must:
- Have a valid certificate.
- Redirect all HTTP traffic to HTTPS - i.e. be HTTPS only.
- Serve all subdomains over HTTPS.
- Serve an HSTS header on base domain:
- Expiry must be at least eighteen weeks (10886400 seconds). The includeSubdomains token must be specified. The preload token must be specified. If you are serving a redirect, that redirect must have the HSTS header, not the page it redirects to.
Does this mean my certificate must be valid for all subdomains, or only that they are available/served over HTTPS? (I have a certificate for sub.example.com, but not the root.)
Can I apply to the HSTS preload list with a subdomain, like sub.example.com?
社区高分解答
原帖链接 · jrtapsell · CC BY-SA 3.0
Do all subdomains need to use HTTPS?
Technically, to be included only the root domain needs to be using HTTPS, but once you get included then any sites under the root domain need to use HTTPS, otherwise connecting will fail, so practically you will want all subdomains to use HTTPS.
Can I apply to the HSTS preload list with a subdomain, like sub.example.com?
No, if you try to test a subdomain you will get the following warning
example.jrtapsell.co.ukis a subdomain. Please preloadjrtapsell.co.ukinstead. (Due to the size of the preload list and the behaviour of cookies across subdomains, we only accept automated preload list submissions of whole registered domains.)
The way this is checked is via a public suffix list, like this one: https://publicsuffix.org/list/
Do I need to use a wildcard certificate to apply for the preload list?
No, as long as the SSL config is valid then you can apply, the certificate type does not matter.
摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。
