legacy.com
HTTPS Everywhere currently rewrites requests to legacy.com (or its subdomains).
Embedded content loaded from third-party domains (for example, YouTube, Google Analytics, ad networks, or CDNs) may also be affected. You can test this by loading the web page in question in a browser with HTTPS Everywhere installed and pulling down the HTTPS Everywhere rules menu. This will show a list of HTTPS Everywhere rules that were applied as the page was loaded, including rules that might have affected embedded content from other domains.
The stable (as yet unreleased) branch contains the following rule that is enabled by default:
<!-- Invalid certificate: - static.cms.legacy.com - connect.legacy.com - www.connect.legacy.com Partially redirects to HTTP: - memorialwebsites.legacy.com Timed out: - legacy.com, equivalent to www.legacy.com --><ruleset name="Legacy.com (partial)"> <target host="legacy.com"/> <target host="www.legacy.com"/> <target host="ak-static.legacy.com"/> <target host="blog.legacy.com"/> <target host="cache.legacy.com"/> <target host="cms.legacy.com"/> <target host="media2.legacy.com"/> <target host="memorialwebsites.legacy.com"/> <!-- Redirects to HTTP --> <exclusion pattern="^http://memorialwebsites\.legacy\.com/(.*/)?(Homepage|InvalidPage)\.aspx"/> <test url="http://memorialwebsites.legacy.com/Homepage.aspx"/> <test url="http://memorialwebsites.legacy.com/InvalidPage.aspx"/> <test url="http://memorialwebsites.legacy.com/mi/Homepage.aspx"/> <test url="http://memorialwebsites.legacy.com/mi/InvalidPage.aspx"/> <target host="mi.legacy.com"/> <target host="mi-cache.legacy.com"/> <target host="mi-static.legacy.com"/> <target host="static.legacy.com"/> <target host="sympathy.legacy.com"/> <securecookie host=".+" name="^optimizely"/> <securecookie host="^\." name="^_ga(?:t?$|t_)"/> <securecookie host="^\w" name=".+"/> <rule from="^http://legacy\.com/" to="https://www.legacy.com/"/> <rule from="^http:" to="https:"/> </ruleset>
The release branch contains the following rules that are disabled by default (so very few users' browsing is likely to be affected by their action):
<!-- Disabled by https-everywhere-checker because: Fetch error: http://mi.legacy.com/ => https://mi.legacy.com/: Too many redirects while fetching 'https://mi.legacy.com/' Fetch error: http://static.legacy.com/ => https://static.legacy.com/: Too many redirects while fetching 'https://static.legacy.com/' CDN buckets: - legacy.o.miisolutions.net Nonfunctional hosts in *legacy.com: - (www.)? ᵈ - static.cms ³ ³ 503 ᵈ Dropped Problematic hosts in *legacy.com: - ak-static ᴬ - (www.)?connect ᵐ - mi-cache ᴬ - mi-static ᴬ ᴬ Akamai / mismatched ᵐ Mismatched Partially covered hosts in *legacy.com: - memorialwebsites * * Some pages redirect to http --><ruleset name="Legacy.com (partial)" default_off="failed ruleset test"> <target host="blog.legacy.com"/> <target host="cache.legacy.com"/> <target host="media2.legacy.com"/> <target host="memorialwebsites.legacy.com"/> <target host="mi.legacy.com"/> <target host="static.legacy.com"/> <target host="sympathy.legacy.com"/> <!-- Redirects to http: --> <exclusion pattern="^http://memorialwebsites\.legacy\.com/(?:.*/)?InvalidPage\.aspx"/> <!-- +ve: --> <test url="http://memorialwebsites.legacy.com/InvalidPage.aspx"/> <test url="http://memorialwebsites.legacy.com/bar/InvalidPage.aspx"/> <test url="http://memorialwebsites.legacy.com/foo/InvalidPage.aspx"/> <securecookie host=".+" name="^optimizely"/> <securecookie host="^\." name="^_ga(?:t?$|t_)"/> <securecookie host="^\w" name=".+"/> <rule from="^http:" to="https:"/> </ruleset>
The HTTPS Everywhere developers welcome corrections and updates to rules. Please see our developer information and documentation of the ruleset format. If filing a bug in the Tor Project's Trac bug tracker, you can use the shared username and password cypherpunks / writecode; please ensure that the bug is marked as applying to HTTPS Everywhere.