Stack Exchange network consists of 183 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.
Visit Stack Exchange
Stack Internal
Knowledge at work
Bring the best of human thought and AI automation together at your work.
Explore Stack InternalWatch out with public TLD's in combination with locally-hosted sites and self-signed certs. For
For example "mysite.dev"mysite.dev with a self-signed certificate was causing a HSTS error in all my browsers (Chrome, Edge and Firefox). When iI switched to a non-public TLD, for example "mysite.localdev"mysite.localdev it worked like a charm.
Watch out with public TLD's in combination with locally-hosted sites and self-signed certs. For example "mysite.dev" with a self-signed certificate was causing a HSTS error in all my browsers (Chrome, Edge and Firefox). When i switched to a non-public TLD, for example "mysite.localdev" it worked like a charm.
Watch out with public TLD's in combination with locally-hosted sites and self-signed certs.
For example mysite.dev with a self-signed certificate was causing a HSTS error in all my browsers (Chrome, Edge and Firefox). When I switched to a non-public TLD, for example mysite.localdev it worked like a charm.
Watch out with public TLD's in combination with locally-hosted sites and self-signed certs. For example "mysite.dev" with a self-signed certificate was causing a HSTS error in all my browsers (Chrome, Edge and Firefox). When i switched to a non-public TLD, for example "mysite.localdev" it worked like a charm.
