5 ms·

Are you using Google Chrome? See this: http://news.ycombinator.com/item?id=2662694 http://news.ycombinator.com/item?id=2662694

WiseWeasel 15y ago
I was using Safari on OS X when I got the error. Sorry for being dense, but could you elaborate on what I should learn from that thread you linked? Is there some kind of solution there, maybe if I was using Chrome, that I might have missed?
- 286c8cb04bda 15y ago
  To summarize the linked thread: Some browsers, when you load an "https" page will complain if any of the elements on that page load over "http". For example, the story above loads some Twitter-y stuff from http://platform.twitter.com http://platform.twitter.com. The technically correct fix is for the site owner to modify the page to load all these resources over https when the page is accessed over https. Until they do that, as a workaround, you could install an extension like the one mentioned by fl3tch[1] to do it in your browser. N.B. That only works if the resource is available over https, many are not. In that case there is no fix. [1] https://www.eff.org/https-everywhere https://www.eff.org/https-everywhere
  - sp332 15y ago
    The technically correct fix is for the site owner to modify the page to load all these resources over https when the page is accessed over https. The easiest way to do that is with protocol-relative URLs. You're probably familiar with relative paths in URLs, e.g. if example.com/test/test.html loads an image at pics/pic1.png, it will really look in https://example.com/test/pics/pic1.png https://example.com/test/pics/pic1.png if you loaded it over https, or http: if you loaded over http. Simple, right? Well, you can use the same idea for absolute paths and even resources from other sites! So if a different site links to the URL //example.com/test/pics/pic1.png (note the lack of protocol before the double-slash), then it will use https: if you loaded the page over https and http: if you loaded it using http.
    - JoshTriplett 15y ago
      Better yet, redirect all http URIs to the corresponding https URIs, and serve everything over https.
      - WickyNilliams 15y ago
        That is not a better approach, there are issues with client-side caching if all resources are served over HTTPS. See http://encosia.com/cripple-the-google-cdns-caching-with-a-single-character/ http://encosia.com/cripple-the-google-cdns-caching-with-a-si...
        JoshTriplett 15y ago
        Easily fixed by serving up a Cache-Control header, as documented in the page you linked to.
blahedo 15y ago
I'm using Firefox and got the same problem. (And the same fix: http works just fine.)

WiseWeasel 15y ago

I was using Safari on OS X when I got the error. Sorry for being dense, but could you elaborate on what I should learn from that thread you linked? Is there some kind of solution there, maybe if I was using Chrome, that I might have missed?

286c8cb04bda 15y ago
To summarize the linked thread: Some browsers, when you load an "https" page will complain if any of the elements on that page load over "http". For example, the story above loads some Twitter-y stuff from http://platform.twitter.com http://platform.twitter.com. The technically correct fix is for the site owner to modify the page to load all these resources over https when the page is accessed over https. Until they do that, as a workaround, you could install an extension like the one mentioned by fl3tch[1] to do it in your browser. N.B. That only works if the resource is available over https, many are not. In that case there is no fix. [1] https://www.eff.org/https-everywhere https://www.eff.org/https-everywhere
- sp332 15y ago
  The technically correct fix is for the site owner to modify the page to load all these resources over https when the page is accessed over https. The easiest way to do that is with protocol-relative URLs. You're probably familiar with relative paths in URLs, e.g. if example.com/test/test.html loads an image at pics/pic1.png, it will really look in https://example.com/test/pics/pic1.png https://example.com/test/pics/pic1.png if you loaded it over https, or http: if you loaded over http. Simple, right? Well, you can use the same idea for absolute paths and even resources from other sites! So if a different site links to the URL //example.com/test/pics/pic1.png (note the lack of protocol before the double-slash), then it will use https: if you loaded the page over https and http: if you loaded it using http.
  - JoshTriplett 15y ago
    Better yet, redirect all http URIs to the corresponding https URIs, and serve everything over https.
    - WickyNilliams 15y ago
      That is not a better approach, there are issues with client-side caching if all resources are served over HTTPS. See http://encosia.com/cripple-the-google-cdns-caching-with-a-single-character/ http://encosia.com/cripple-the-google-cdns-caching-with-a-si...
      - JoshTriplett 15y ago
        Easily fixed by serving up a Cache-Control header, as documented in the page you linked to.

blahedo 15y ago

I'm using Firefox and got the same problem. (And the same fix: http works just fine.)