Skip to content
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

Closed
stof opened this issue Nov 5, 2019 · 1 comment · Fixed by #409
Closed

Loading the blog with https is broken due to mixed content #401

stof opened this issue Nov 5, 2019 · 1 comment · Fixed by #409

Comments

@stof
Copy link
Contributor

stof commented Nov 5, 2019

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.

@nex3
Copy link
Contributor

nex3 commented Nov 12, 2019

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.

nex3 added a commit that referenced this issue Nov 13, 2019
Logdown seems to be basically unmaintained, its servers are
unreliable, and it's been causing some mixed-content errors lately.
This moves all blog posts to sass-lang.com itself; I'll set up
redirects from the blog as best I can once this lands.

Closes #401
Closes #402
Closes #403
@nex3 nex3 closed this as completed in #409 Dec 18, 2019
tatianamac pushed a commit to tatianamac/sass-site that referenced this issue Dec 19, 2019
Logdown seems to be basically unmaintained, its servers are
unreliable, and it's been causing some mixed-content errors lately.
This moves all blog posts to sass-lang.com itself; I'll set up
redirects from the blog as best I can once this lands.

Closes sass#401
Closes sass#402
Closes sass#403
asaf400 pushed a commit to asaf400/ass-site that referenced this issue Apr 18, 2024
Logdown seems to be basically unmaintained, its servers are
unreliable, and it's been causing some mixed-content errors lately.
This moves all blog posts to sass-lang.com itself; I'll set up
redirects from the blog as best I can once this lands.

Closes sass#401
Closes sass#402
Closes sass#403
asaf400 pushed a commit to asaf400/ass-site that referenced this issue Apr 18, 2024
Logdown seems to be basically unmaintained, its servers are
unreliable, and it's been causing some mixed-content errors lately.
This moves all blog posts to sass-lang.com itself; I'll set up
redirects from the blog as best I can once this lands.

Closes sass#401
Closes sass#402
Closes sass#403
asaf400 pushed a commit to asaf400/ass-site that referenced this issue Apr 18, 2024
Logdown seems to be basically unmaintained, its servers are
unreliable, and it's been causing some mixed-content errors lately.
This moves all blog posts to sass-lang.com itself; I'll set up
redirects from the blog as best I can once this lands.

Closes sass#401
Closes sass#402
Closes sass#403
asaf400 pushed a commit to asaf400/ass-site that referenced this issue Apr 18, 2024
Logdown seems to be basically unmaintained, its servers are
unreliable, and it's been causing some mixed-content errors lately.
This moves all blog posts to sass-lang.com itself; I'll set up
redirects from the blog as best I can once this lands.

Closes sass#401
Closes sass#402
Closes sass#403
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants