3 ms·
The problem this DOESN'T solve is that if the resource is not availale over SSL, then this won't work at all and will show broken links. I've got a project tha
by bgmd 14y ago
The problem this DOESN'T solve is that if the resource is not availale over SSL, then this won't work at all and will show broken links.
I've got a project that addresses this by converting any URL to SSL:
http://www.fixweb.co/
Just take whatever URL you want to access, like
http://example.com/test.gif
add the FixWeb.co address in front of it like this:
https://fixweb.co/example.com/test.gif
^^^^^^^^^^^^^^^^^^
and it will return the file over SSL.
It's not designed for high security file delivery, obviously, but it will get you around a normal Mixed-Content warning.
- pronoiac 14y agoOh look, you just implemented an open proxy. Those are rather prone to abuse, aren't they?
- jbrechtel 14y agoWhen would someone use this? If my content isn't available over HTTPS already then it's likely due to not wanting to support the load...in which case I'm not going to assume yours will handle it. Or do you see this as more of an end user fix via a MITM proxy or something? Even then that sounds contrived. What am I missing?