Skip to content
This repository has been archived by the owner on Nov 6, 2023. It is now read-only.

Microsoft ruleset is differentially broken in Chrome vs Firefox #507

Closed
pde opened this issue Aug 28, 2014 · 2 comments
Closed

Microsoft ruleset is differentially broken in Chrome vs Firefox #507

pde opened this issue Aug 28, 2014 · 2 comments

Comments

@pde
Copy link
Contributor

pde commented Aug 28, 2014

We've had some persisten problems with the breakage in the Microsoft ruleset. However I'm seeing something stranger on this page:

http://windows.microsoft.com/en-us/windows7/security-checklist-for-windows-7

In chrome, the page's CSS is completely broken. In firefox 4.0.0 (which should be the same ruleset), it's fine. I don't see mixed content indications in Chrome. We should figure out what's causing this.

@pde pde added bug labels Aug 28, 2014
@pde
Copy link
Contributor Author

pde commented Aug 28, 2014

Possible cause:

GET https://a248.e.akamai.net/f/1737/7533/6/res2.windows.microsoft.com/resources/4.2/wol/shared/css/windows8_site_ltr.css net::ERR_CONNECTION_REFUSED security-checklist-for-windows-7:59
GET https://a248.e.akamai.net/f/1737/7533/6/res2.windows.microsoft.com/resbox/en/windows/main/15d2470f-0fcf-45e9-bf5b-c943236a61cf_242.css net::ERR_CONNECTION_REFUSED

(some subsequent image loads are also blocked...)

@pde
Copy link
Contributor Author

pde commented Aug 28, 2014

This wasn't solely an HTTPS Everywhere bug... looks like it was caused by an interaction between this rule and AdAway running on the phone I was tethering with. Firefox wasn't running through that proxy.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant