• Please remove explicit http: from script urls
    1 replies, posted
(I hope this is the right section and it hasn't been posted before because I have no idea what to search for to check.) [img]https://dl.dropboxusercontent.com/u/5013896/forum/Facepunch/Fast%20Threads/11.2013/Firefox%20hat%20unsichere%20Inhalte%20blockiert..png[/img] This is what happens when opening The Ticker through https or if there's a [noparse][HD][/noparse] tag in a thread. Both don't work without manually deactivating the mixed active content blocker for each tab. The warning shows up elsewhere too but doesn't seem to affect functionality. It would be great if someone could change the scripts with explicit "http://" to just "//" so they are loaded with TLS too if the main page is.
I've had issues like this with Youtube. Try HTTPS Everywhere, it cascades across a page to make everything encrypted where possible.
Sorry, you need to Log In to post a reply to this thread.