If you browse JLSE on HTTPS, the furigana JS doesn't load.

This is because the furigana JS is served as http://sstatic.net/js/third-party/japanese-l-u.js?v=6 instead of as https:// ...

Since sstatic.net seems to support HTTPS just fine, I think this should probably not be too difficult to fix for whoever is responsible for these sort of things.

  • 1
    FWIW, HTTPS still isn't fully supported on Stack Exchange. I know this because recently someone accidentally enabled HTTPS on Stack Exchange in the HTTPS Everywhere plugin, and people complained about not being able to use the site: meta.stackexchange.com/questions/214968/… – snailplane Feb 5 '14 at 20:03

This specific JS file is now being served via a schemaless URL, meaning it works for http and https.


You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .