ajc.com
HTTPS Everywhere currently rewrites requests to ajc.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:
<!-- Other Atlanta Journal Constitution rulesets: * MyAJC.com.xml Numerous unsupported subdomains (>300 found by Sublist3r) Mixed content on some www.ajc.com pages --><ruleset name="AJC.com (partial)"> <target host="ajc.com"/> <target host="www.ajc.com"/> <target host="myaccount.ajc.com"/> <target host="store.ajc.com"/> <target host="subscribe.ajc.com"/> <rule from="^http:" to="https:"/> </ruleset>
The release branch contains the following rules that are enabled by default:
<!-- Other Atlanta Journal Constitution rulesets: * MyAJC.com.xml Numerous unsupported subdomains (>300 found by Sublist3r) Mixed content on some www.ajc.com pages --><ruleset name="AJC.com (partial)"> <target host="ajc.com"/> <target host="www.ajc.com"/> <target host="myaccount.ajc.com"/> <target host="store.ajc.com"/> <target host="subscribe.ajc.com"/> <!-- Rewrite rule must touch https to fix errors caused by the site adding https to links that do not support it. When a user requests a page on https://www.ajc.com, it often seems to add https to other ajc.com links on that page regardless of whether or not the subdomain supports https. This can be a problem because clicking on a https://ajc.com link results in an invalid cert error. The rule fixes this by rewriting https://ajc.com links (which don't support https) to https://www.ajc.com links (which do support https). Example: https://www.ajc.com/news/local/woman-emory-doctors-left-camera-body-after-surgery/Ajt6yMsjByDAWJTLfkDCyM/ The Most Read sidebar on the above page (or most any other page) is an example of behavior that necessitates the rule. https://ajc.com links are created despite it not supporting https. Visiting that page and clicking on one of the https://ajc.com links on the sidebar (while the below rule is disabled) should reproduce the issue. --> <rule from="^https?://ajc\.com/" to="https://www.ajc.com/"/> <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.