Again, the problem is that ABP sees the original and rewritten URLs as separate requests, so if only the original URL is whitelisted, the rewritten URL (which is the one really requested on the network) will still be blocked and trigger the symptom in question.
I verified that "the rewritten URL returns correct content" by browsing directly to
https://a248.e.akamai.net/f/259/1/g/tia ... =4.0-beta3 (does it return any error for you?)
Rules of this kind are
quite common for content hosted on the Akamai CDN but not configured with custom SSL. As far as I know, they have not historically caused many bugs.
As I stated, whitelisting both URLs in ABP successfully resolves the issue for me, with
no configuration changes needed to HTTPS Everywhere. That means that as long as the offending script is allowed to load from
either URL, the page will work.
I have also verified that HTTPS Everywhere by itself, with no form of ad blocking active, causes no problems for the page in question. That is the sense in which the ruleset is working correctly.
(For clarity: I am using Firefox, and I do not know how the situation might differ in Chrome.)