Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Mixed content issue for HTTP rel="next" links in Firefox

See original GitHub issue

Issue Summary:

Firefox treats HTTP rel=“next” links as “mixed content”, blocks those and displays a yellow triangle on the green padlock in front of the URL.

Steps to Reproduce:

In Firefox, visit https://hannah.wf/
Notice that there is a yellow triangle on the green padlock due to mixed content.
Press Shift+F5 to open developer tools. Click on “Console”. The following is shown:
```
Blocked loading mixed active content "http://hannah.wf/page/2/"
```
View page source and notice this line: <link rel="next" href="http://hannah.wf/page/2/" />

Expected result:

Green padlock only.

Actual result:

Green padlock with yellow triangle.

Technical details:

Platforms where the issue observed:

Ghost Version: 0.7
Browser: Firefox Version 43

Issue Analytics

State:
Created 8 years ago
Comments:16 (14 by maintainers)

Top GitHub Comments

1reaction

howsonwhocodescommented, Jan 4, 2016

@hwdsl2 - a work around is to set the blog url to use SSL. E.g https://www.example.com in config.js - if you use nginx and get stuck in a loop add proxy_set_header X-Forwarded-Proto $scheme; to your location configuration. It does force your entire site over HTTPS mind, depends what you are after but does stop the mixed content issue for now.

0reactions

ErisDScommented, Jan 25, 2016

👍