BBC iPlayer renders weirdly

Using the HTTPS Everywhere plugin on the site www.bbc.co.uk/iplayer causes the site to render badly. I believe that this is a bug in the BBC handling of the request but it appears that the site should be added to a whitelist.

N.B. I believe that the BBC uses GeoIP locating to differentiate between UK and non-UK addresses so different results may be found when testing this from outside the UK.

changed milestone to %HTTPSE Cr 2013.4.2x

added component::https everywhere/eff-https everywhere httpse-ruleset-bug milestone::HTTPSE Cr 2013.4.2x owner::MB parent::6975 priority::medium resolution::fixed status::closed type::defect labels

MB, can you look at this? I don't have a shell or proxy handy in the UK.

Trac:
Owner: pde to MB
Keywords: N/A deleted, httpse-ruleset-bug added
Summary: httpse-ruleset-bug BBC iPlayer to BBC iPlayer
Status: new to assigned

Trac:
Summary: BBC iPlayer to BBC iPlayer renders weirdly

Chrome or Firefox? Which version of https everywhere? With or without using Tor Browser Bundle? Does it already happen on the first time you load www.bbc.co.uk/iplayer ?

Could not reproduce problem with Firefox 18.0.2 on Ubuntu with https everywhere 4.0development.5 from outside the UK. Could not reproduce problem with Chrome 24.0.1312.69 on Ubuntu with https everywhere 2013.1.18 from outside the UK.

Could not reproduce problem with TorBrowserBundle (Firefox 10.0.12 ESR), neither with 

StrictNodes 1
ExitNodes {gb}

(recognized as being in the UK), nor from outside the UK.

Trac:
Username: martin__

Replying to cypherpunks:

Using the HTTPS Everywhere plugin on the site www.bbc.co.uk/iplayer causes the site to render badly.

I see nothing amiss. You'll need to be more specific.

Trac:
Username: MB
Status: assigned to needs_information

Hi

I am using google Chrome Version 24.0.1312.57 on a MacBook 4,1 system version 10.7.5 and the EFF Https everywhere plugin from the chrome app store.

Since you had trouble replicating this I wiped all Chrome data from my account thereby delating all extensions, cookies and settings. I then loaded the https everywhere plugin again and went to www.bbc.co.uk/iplayer from a UK internet connection. Surprisingly I then found that the page appeared fine but upon refreshing it it rendered badly again with a complaint that a browser with CSS support was needed to show the page. Using the inspect chrome tool I found a single cookie being placed on the initial visit. One of the values stored in this cookie is "BBC-UID", deleting the BBC-UID value caused the page to be rendered properly again after refresh. The problem appears again in subsequent refreshes.

Trac:

Rendering bug with cookies displayed

Hypothesis: this might be an insance of #7492 (moved), which is wildly overdue for a fix. I've started working on it, despite theoretically being on vacation.

Can anyone report whether this problem is still occurring?

Hi

I can confirm this issue is still present as described previously with latest Chrome version and latest chrome web store HTTPS Everywhere plugin

Trac:
Milestone: N/A to HTTPSE Cr 2013.4.1x

This was a simple instance of #6975 (moved), sorry for not being on it sooner.

Trac:
Status: needs_information to closed
Parent: N/A to #6975 (moved)
Resolution: N/A to fixed

closed

moved to tpo/applications/https-everywhere-eff#8216 (closed)