You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
click.e.twitter.com (in Twitter marketing emails) inappropriately HTTPS-ified #7137
Twitter's marketing emails contain links to http://click.e.twitter.com/, which redirect to the actual target. For instance, an email about live streams of the US presidential debate has the following link: Watch live.
HTTPS Everywhere ships with a rule which matches this domain and https-ifies it, but the server serves a certificate only valid for a248.e.akamai.net, *.akamaized.net, *.akamaihd-staging.net, *.akamaihd.net, *.akamaized-staging.net.
(For what it's worth, click.e.twitter.com is a CNAME for click.virt.s7.exacttarget.com, a service run by Salesforce – which in turn is a CNAME for Akamai – rather than this being a tracking system run by Twitter themselves.)
(Preferred but more work) Rewrite Twitter.xml to not use a wildcard target. Wildcards are discouraged by the style guide, in part because they can break subdomains like we're seeing here.
(Less preferred, less work) Add click\.e to the exclusion tag with an appropriate test.
Unfortunately, no. #6681 (comment) describes some approaches. For this specific issue though, for option (1), it would be enough to use the test URLs already in the ruleset.
Activity
jeremyn commentedon Sep 27, 2016
Thanks for the report.
Twitter.xmlis the ruleset that matchesclick.e.twitter.com, specifically:There are at least two possible fixes:
Twitter.xmlto not use a wildcard target. Wildcards are discouraged by the style guide, in part because they can break subdomains like we're seeing here.click\.eto the exclusion tag with an appropriate test.wjt commentedon Sep 28, 2016
@jeremyn I guess there's no analytics mechanism by which one could see which domains are, in practice, being matched by the wildcard?
jeremyn commentedon Sep 28, 2016
Unfortunately, no. #6681 (comment) describes some approaches. For this specific issue though, for option (1), it would be enough to use the
testURLs already in the ruleset.J0WI commentedon Oct 24, 2016
closed by #7416