Clever Geek Handbook

Self signed certificate rejected by chrome

Lately, I've started to notice this behavior. Even after accepting the certificate, it turns out to be invalid by the browser when switching to and from an insecure endpoint. For example:

  • Go to https://example.com
  • Accept certificate (Chrome displays NET :: ERR_CERT_COMMON_NAME_INVALID as the reason the certificate is invalid)
  • Redirected to http://example.com
  • Go to https://example.com/secure_url
  • Loading the start page works fine, but as a result of loading this page, the certificate seems invalid and we get net :: ERR_INSECURE_RESPONSE in chrome.
  • If the page is refreshed, we have to accept the certificate again, at which point all the assets that have not been loaded are available again.

This issue doesn't seem to happen in Firefox and is not reported in any other browser. Shouldn't you be limited to accepting a certificate only once per session? Has Chrome's behavior changed in this case?

Problem in Chrome

+3
google-chrome ssl-certificate


source to share


No one has answered this question yet

See similar questions:

111
Determine if the ajax call caused an unsafe response or connection refused

or similar:

1554
Disable Chrome cache for website development
1403
Disable Same Origin Policy in Chrome
1153
How do I get ASP.NET Web API to return JSON instead of XML using Chrome?
1146
How to create a self-signed certificate with OpenSSL
1058
Getting Chrome to accept self-signed local certificate
949
How to remove border (outline) around text / input fields? (Chromium)
266
Unusual error in Chrome Developer Console - Failed to load resource: net :: ERR_CACHE_MISS
nine
Self-signed certificate
five
Chrome NET :: ERR_CERT_AUTHORITY_INVALID error when self signed certificate in LocalHost
0
How to install a self-signed SSL certificate on OS X High Sierra


More articles:


All Articles
Loading...
X
Show
Funny
Dev
Pics