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?