Closed lll000111 closed 5 years ago
@lll000111, thanks for the heads up!
We're currently loading JS and CSS assets with http
absolute paths. So any forced redirects to https
is going to throw a Mixed Content
error. We have a PR open here to have this fixed soon :)
Looks like it's now all working fine on my end. Closing this. Thanks for the reports all 👍
The subject says it.
Firefox and Chrome seem to FORCE https now. manually attempting to load via
http://
does not work: https://security.googleblog.com/2018/02/a-secure-web-is-here-to-stay.htmlFirefox:
Chrome:
When I try to proceed anyway (both FF and Chrome) I end up with
IE Edge: the same.
Possibly relevant:
https://blog.github.com/2018-05-01-github-pages-custom-domains-https/#configuring-your-domain