Opened 8 years ago

Closed 8 years ago

#4209 closed defect (fixed)

wordpress.org broken: css not loaded

Reported by: ibotty Owned by: pde
Priority: Medium Milestone:
Component: HTTPS Everywhere/EFF-HTTPS Everywhere Version:
Severity: Keywords:
Cc: https-everywhere@…, gange@…, alexgieg@…, schoen Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

in a way, this is entirely wordpress.org's fault, because though they offer their css files encrypted, they use the http-link even though accessed through https. https everywhere now seems not to allow loading this file (firebug shows it not loading).

i have contacted their webmasters, but i don't hold my breath ;).
i have not looked at https everywhere in a while, so maybe this is not yet possible, but it would be great, if it could rewrite the stylesheet url.

(as i can not select the version for https everywhere in the version field: this is on 1.0.3)

Child Tickets

Change History (3)

comment:1 Changed 8 years ago by pde

Cc: https-everywhere@… gange@… alexgieg@… schoen added
Status: newaccepted

CC'ing people who've hacked on this ruleset.

The problem appears to be as follows:

WordPress embeds a CSS file like this one: http://www.wordpress.org/style/wp4.css?12

We <a href="https://gitweb.torproject.org/https-everywhere.git/blob/1.1:/src/chrome/content/rules/WordPress.xml">rewrite</a> that to https://s-ssl.wordpress.com but that server has stopped working.

Currently it seems that a rewrite to https://www.wordpress.org/style/wp4.css?12 instead would fix the problem.

Question: do we know if there are any other things that s-ssl.wordpress.com|org are being used for, where a rewrite to https://www.wordpress.com would cause problems?

comment:2 Changed 8 years ago by pde

I've tried this commit, which appears to fix things:

https://gitweb.torproject.org/https-everywhere.git/commitdiff/b9206653fd7d83c0a1428fce256773769eb9661b

However we could use a bit of testing to make sure it doesn't break anything else.

comment:3 Changed 8 years ago by pde

Resolution: fixed
Status: acceptedclosed

The fix for this went out in the 1.2 stable release.

Note: See TracTickets for help on using tickets.