7 ms·
The site runs over https but loads leaflet over http, so that it get's blocked at least by recent versions of Firefox, Chrom[e/ium] and Internet Explorer. http
by phaer 12y ago
The site runs over https but loads leaflet over http, so that it get's blocked at least by recent versions of Firefox, Chrom[e/ium] and Internet Explorer.
https://developer.mozilla.org/en-US/docs/Security/MixedContent/How_to_fix_website_with_mixed_content https://developer.mozilla.org/en-US/docs/Security/MixedConte...
- finnn 12y agoActually the link was an http link. You likely have HTTPS Everywhere that changed that.
- stereo 12y agoIt’s still nice, if all the content is available over both http and http, to use protocol-relative URLs, i.e. without http or https before the //: part. It looks like the author has read your comment, and updated his source code to say <script src="//cdnjs.cloudflare.com/ajax/libs/leaflet/0.7.3/leaflet.js”> for leaflet. http://www.paulirish.com/2010/the-protocol-relative-url/ http://www.paulirish.com/2010/the-protocol-relative-url/ describes how protocol-relative URLs work.
- phaer 12y agoYou are right, I missed that. But you should have protocol relative urls on servers which run https.
- finnn 12y agoIt's not my site. I'd force everyone to https if it was