[HTTPS-E Rulesets] new rule

[Drake, Brian]

Anyone checking this rule should know that it’s covered by the existing
WordPress rule, but that is disabled by default because of mixed content.

I just followed the HTTP and HTTPS links provided (see below) and had a
quick look. On HTTPS: there is no mixed content blocking and the “Home” tab
is not highlighted. Otherwise, it seems fine.

The dots in the “from” value should be escaped
(^http://maggiemcneill\.wordpress\.com/);
as it is, the dots would match any character. With that correction made, I
would not be able to just click on it to visit the HTTP version.

--
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.

On Thu, Jan 16, 2014 at 0305 (UTC), John David Galt <
jdg at diogenes.sacramento.ca.us> wrote:

> <ruleset name="Maggie McNeill">
>   <target host="maggiemcneill.wordpress.com" />
>
>   <rule from="^http://maggiemcneill.wordpress.com/" to="
> https://maggiemcneill.wordpress.com/"/>
> </ruleset>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.eff.org/pipermail/https-everywhere-rules/attachments/20140127/d1c9742d/attachment.html>