<div dir="ltr"><div>Actually, you should probably forget what I said about platform=mixedcontent. HTTPS Everywhere supports other browsers too, and I don’t know how they behave.<br><br></div>Once again, I hope someone who understands this software better can help us.<br>
<div><div><div class="gmail_extra"><br clear="all"><div><div dir="ltr"><div>--<br>Brian Drake<br><br>All content created by me: <a href="http://www.wipo.int/treaties/en/ip/berne/trtdocs_wo001.html" target="_blank">Copyright</a> © 2014 Brian Drake. All rights reserved.<br>
</div></div></div>
<br><div class="gmail_quote">On Tue, Jan 14, 2014 at 0855 (UTC), Drake, Brian <span dir="ltr"><<a href="mailto:brian@drakefamily.tk" target="_blank">brian@drakefamily.tk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div><div>I wasted lots of time on this issue too (but on a different site).<br><br></div>As far as Firefox is concerned, an insecure request is an insecure request; it doesn’t care if HSTS rewrites it [1], and presumably, it doesn’t care if HTTPS Everywhere rewrites it either. Can someone more familiar with how HTTPS Everywhere works internally confirm this?<br>

<br></div>I guess you’re supposed to use platform=mixedcontent here.<br><div><div><div><div class="gmail_extra"><br>[1] <a href="https://blog.mozilla.org/tanvi/2013/04/10/mixed-content-blocking-enabled-in-firefox-23/" target="_blank">https://blog.mozilla.org/tanvi/2013/04/10/mixed-content-blocking-enabled-in-firefox-23/</a> (appendix, section 4: “Relying on HSTS to prevent Mixed Content”)<br>

<br clear="all"><div><div dir="ltr"><div>--<br>Brian Drake<br><br>All content created by me: <a href="http://www.wipo.int/treaties/en/ip/berne/trtdocs_wo001.html" target="_blank">Copyright</a> © 2014 Brian Drake. All rights reserved.<br>

</div></div></div>
<br><div class="gmail_quote"><div class="im">On Fri, Jan 3, 2014 at 0054 (UTC), James Cox <span dir="ltr"><<a href="mailto:james@cox.cx" target="_blank">james@cox.cx</a>></span> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div class="im">
<div>Hi All,<br>
<br>
 I'm trying to write a rule to fix a problem I have with a page that<br>
has "mixed active content". I can see in Firefox Console the URL that<br>
is being blocked, but when I try to make a simple ruleset to match<br>
this URL it doesn't seem to be running.<br>
<br>
Here's a screenshot of what I'm seeing in the Firefox Console:<br>
<a href="http://i.imgur.com/DuwLO2X.jpg" target="_blank">http://i.imgur.com/DuwLO2X.jpg</a><br>
<br>
And here's my rule file:<br>
<ruleset name="Conducive"><br>
  <target host="<a href="http://apps.conducive.com.au" target="_blank">apps.conducive.com.au</a>" /><br>
  <rule from="^<a href="http://apps" target="_blank">http://apps</a>\.conducive\<br>
.com\.au:443"<br>
to="<a href="https://apps.conducive.com.au:443" target="_blank">https://apps.conducive.com.au:443</a>"/><br>
</ruleset><br>
<br>
Any hints would be greatly appreciated.<br>
Thanks,<br>
James<br></div></div>
[snip]<a href="https://lists.eff.org/mailman/listinfo/https-everywhere" target="_blank"></a><br>
</blockquote></div></div></div></div></div></div>
</blockquote></div></div></div></div></div>