[HTTPS-Everywhere] A bug with 0.9.0

[Seth David Schoen]

souihliw writes:

> Hi EFF team,
> thx for all what you're doing :)
> In fact i added a rule for the the website flickr which is censored in
> Tunisia and everything went well with the version 0.2.2 but after the update
> the feature has been dis-activated and it disappeared from the list  :/
> Looking forward to your answer!

Hi,

The update replaces all existing rules in the chrome/content/rules
directory.  It's not supposed to replace rules in HTTPSEverywhereUserRules,
however.

Some users have had trouble with the fact that the rule format has
changed since earlier versions and it is now mandatory to include
<target host> elements indicating which hosts the rules apply to.
The <target host> mechanism is described at

https://www.eff.org/https-everywhere/rulesets

In the current version of HTTPS Everywhere, if a rule doesn't contain
a <target host>, it's considered invalid (or, one could say,
inapplicable) and is ignored.

I'm very curious about your Flickr rule.  For me, https://flickr.com/
and https://www.flickr.com/ don't work at all.  Maybe you're rewriting
http://flickr.com/ to go through an HTTP proxy or something?  Or do
you know an official Flickr URL that supports HTTPS access?

-- 
Seth Schoen
Senior Staff Technologist                         schoen at eff.org
Electronic Frontier Foundation                    https://www.eff.org/
454 Shotwell Street, San Francisco, CA  94110     +1 415 436 9333 x107