https-everywhere-rules-raw-4.0: vendor/https-everywhere/src/chrome/content/rules/McAfee.xml
<!-- Av vendor. promos.mcafee.com lacks https -->
<ruleset name="McAfee (buggy)" default_off="Rediects to http, buggy">
<target host="mcafee.com" />
<target host="*.mcafee.com" />
<!--
This redirects to http. As in the
case below, after we give up (good),
we don't try again when it redirects
to something that we can secure (bad).
Bug: https://trac.torproject.org/projects/tor/ticket/5686
-->
<exclusion pattern="^https?://(www\.)?mcafee\.com/error-pages/404\.aspx" />
<target host="mcafeesecure.com" />
<target host="www.mcafeesecure.com" />
<target host="images.scanalert.com" />
<!-- If we fetch a cookie over http,
we don't secure it, so there's
no need to play acrobatics in
order to avoid doing so.
-->
<securecookie host="^(.*\.)?mcafee\.com$" name=".*" />
<!-- /$ redirects to http. We give
up, let it redirect to us/, and
don't rewrite to https once there.
Bug: https://trac.torproject.org/projects/tor/ticket/5686
-->
<rule from="^https?://(?:www\.)?mcafee\.com/$"
to="https://www.mcafee.com/us/" />
<rule from="^http://(?:www\.)?mcafee\.com/"
to="https://www.mcafee.com/" />
<rule from="^http://(blogs|home|(?:secure)?images|shop|us)\.mcafee\.com/"
to="https://$1.mcafee.com/" />
<!-- At least the homepage redirects to http. -->
<rule from="^http://service\.mcafee\.com/(css/|images/|js/|locale/|(?:Script|Web)Resource\.axd)"
to="https://service.mcafee.com/$1" />
<rule from="^http://images\.scanalert\.com/"
to="https://images.scanalert.com/" />
<rule from="^http://www\.mcafeesecure\.com/"
to="https://www.mcafeesecure.com/" />
</ruleset>