News for hackers. Stuff that matters.

A comment on Protocol-Relative URLs to Fix Mixed-Content Warnings.

Re:Protocol-Relative URLs to Fix Mixed-Content Warnings by bgmd on Thursday September 13, 2012 @10:38PM (#4519746)
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.

[ Parent | on HN ]
Re:Protocol-Relative URLs to Fix Mixed-Content Warnings by pronoiac on Friday September 14, 2012 @04:46AM (#4520786)
Oh look, you just implemented an open proxy. Those are rather prone to abuse, aren't they?
[ Parent | on HN ]
Re:Protocol-Relative URLs to Fix Mixed-Content Warnings by jbrechtel on Friday September 14, 2012 @07:01AM (#4521065)
When 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?

[ Parent | on HN ]