3 ms·
"Be aware that inclusion in the preload list cannot really be undone. You can request to be removed, but it will take months for the deleted entry to reach user
by jtchang 11y ago
"Be aware that inclusion in the preload list cannot really be undone. You can request to be removed, but it will take months for the deleted entry to reach users with a Chrome update and we cannot make guarantees about other browser vendors."
So basically once you submit it your domain is forever HTTPS on Chrome? I'm sure there are cases that might warrant HTTP. Mostly though the cases I am coming up with are mostly testing or implementation speed. It is generally easier to stand up HTTP than HTTPS. At least for now until Lets Encrypt is standard.
- gcp 11y agoSo basically once you submit it your domain is forever HTTPS on Chrome? Yes, and Firefox too since they share the preload lists. Mostly though the cases I am coming up with are mostly testing or implementation speed. It is generally easier to stand up HTTP than HTTPS. At least for now until Lets Encrypt is standard. That sounds more of an issue for new domains, rather than established ones, no? I mean once you set up an inverse proxy like nginx to handle the HTTPS side, that should disappear.