Re: [HTTPS-Everywhere] wrong FAQ "Q. Why use a whitelist of sites that support HTTPS?"

The ruleset page [1] gives the obsolete Wikipedia example (but at least it notes that it’s obsolete). See my previous message for examples that could replace it. Further down, the text “secure flag” links to the deprecated Wikimedia secure server. Both of these should be changed. [1] https://www

Re: [HTTPS-Everywhere] Random site fails - GIF dance party

To summarise the last two messages: The Amazon Web Services ruleset (AmazonAWS.xml) contains this rule: https://$1.s3.amazonaws.com/"; /> which breaks this site: http://fuzzywobble.s3-website-us-east-1.amazonaws.com/ Erik suggested labelling the ruleset as “partial” and disabling it by default

Re: [HTTPS-Everywhere] Mailing List Servers

Old URLs that point to mail1.eff.org (or mail2.eff.org?) no longer work. I found one that did not work but did work when I changed it to lists.eff.org. Is it possible to set up the relevant redirects on mail[12]? -- Brian Drake All content created by me: Copyright

Re: [HTTPS-Everywhere] Outdated FAQ answer: “Q. What's the meaning of the broken padlock icon at the bottom of the browser …”

The last point I raised – mixed content blocking – deserves more attention. The answer currently says, in part: > although Chrome version 18+ has some built-in protections against insecure > scripts in pages, and HTTPS Everywhere for Chrome will in fact trigger > these on a site like the New York

Re: [HTTPS-Everywhere] [HTTPS-E Rulesets] HTTPS Everywhere 3.4.5 / Chrome 2014.1.3 released

It used to be that you could have an add-on listing on Mozilla Add-ons but distribute the add-on itself through another site. But I can’t find any mention of that now. Did they get rid of that? There’s an add-on on Mozilla Add-ons called HTTP Nowhere [1]. It sounds good, is licensed under GPL 3.0