|
|
|
|
|
by dinosaurdynasty
1478 days ago
|
|
This sounds like if you create a custom CA, import it, create a cert for localhost, and then connect Chrome to https://localhost and it sends an HSTS header that Chrome accepts. Which is something you probably shouldn't be doing in the first place. Browsers aren't supposed to accept HSTS on self-signed certs so connecting to a self signed localhost shouldn't do this. |
|
There's nothing against self signed certificates working with HSTS at all. It's perfectly fine for browsers to accept HSTS regardless of who signed it.