Timeline for My Chrome "jumps" to non-existent HTTPS protocol
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 10, 2019 at 14:50 | comment | added | tutuca | chrome://net-internals/#hsts is disabled in newer versions of crhome | |
| Mar 3, 2015 at 23:56 | comment | added | lbarman | Great ! it was this. Did not know that HSTS sticked, and I thought the "no caching" option of dev-tools was performing a clean state. Great input. For the record, I did not setup my Apache server to send HSTS, so it seems sufficient that at one point, an address is accessible via HTTPS for chrome to remember it and "force SSL" via HSTS later on. | |
| Mar 3, 2015 at 23:54 | vote | accept | lbarman | ||
| Mar 3, 2015 at 18:46 | history | answered | Daniel B | CC BY-SA 3.0 |