-
Notifications
You must be signed in to change notification settings - Fork 230
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Loading the blog with https is broken due to mixed content #401
Comments
Thanks for reporting this! Unfortunately, I'm not sure if there's anything we can do about this on our end. Logdown assets don't seem to support HTTPS, and we don't have any way of configuring the main page to force HTTP. It may just be time to bite the bullet and move the blog to the main Sass website. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The blog has a valid TLS certificate, and so Google considers it accessible on HTTPS and will use it for its search result links, which is how I discovered the issue and is what makes it an actual problem.
When loading the blog in HTTPS, mixed content restrictions are blocking the CSS and JS files, as well as warnings for the favicon (which are broken anyway due to being a 404).
Favicon URLs should be an easy fix, as they are URLs on sass-lang.com which support HTTPS. I don't know whether logdown assets can be fixed easily or whether it is an issue of the platform.
The text was updated successfully, but these errors were encountered: