[HTTPS-E Rulesets] ACM.org

Drake, Brian brian at drakefamily.tk
Wed Jan 15 05:16:11 PST 2014


In the ACM.org ruleset [1], there is a comment that says that we secure all
mixed content requests and, therefore, it should not be marked mixedcontent.

However, it still is marked mixedcontent.

Is this the accepted workaround for the mixed content blocker not allowing
the requests to get to us [2]?

[1]
https://gitweb.torproject.org/https-everywhere.git/blob/HEAD:/src/chrome/content/rules/ACM.org.xml
[2]
https://lists.eff.org/pipermail/https-everywhere/2014-January/001901.html

--
Brian Drake

All content created by me:
Copyright<http://www.wipo.int/treaties/en/ip/berne/trtdocs_wo001.html>©
2014 Brian Drake. All rights reserved.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.eff.org/pipermail/https-everywhere-rules/attachments/20140115/f22500ae/attachment.html>


More information about the HTTPS-Everywhere-Rules mailing list