Opened 8 years ago

Closed 8 years ago

#7888 closed defect (fixed)

Music does not play properly in Spotify Web Player with current ruleset enabled

Reported by: cypherpunks Owned by: MB
Priority: High Milestone:
Component: HTTPS Everywhere/EFF-HTTPS Everywhere Version:
Severity: Keywords: httpse-ruleset-bug
Cc: hugoh@… Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


Music does not play back on the Spotify web player if any rules are enabled. Disabling the rules or the entire extension fixes the problem and enables music playback.

Current guess is that the ruleset needs to be updated to accomodate the site.

Please reference this thread for additional details:

Child Tickets

Change History (11)

comment:1 Changed 8 years ago by pde

Priority: normalmajor

comment:2 Changed 8 years ago by pde

Owner: changed from pde to MB
Status: newassigned

comment:3 Changed 8 years ago by hugoh

Cc: hugoh@… added

The rule that seems to break it is Cloudfront. Disabling it works around this issue.

comment:4 Changed 8 years ago by mikeperry

Keywords: httpse-ruleset-bug added

comment:5 Changed 8 years ago by pde

Hi Hugoh, if you look at Developer Tools -> Network, you should be able to see which cloudfront subdomains Spotify on Chrome OS is talking to. If you do that, I will try excluding those subdomains from the spotify ruleset.

comment:6 Changed 8 years ago by pde

I mean "from the Cloudfront ruleset", there is no spotify ruleset of course.

comment:7 Changed 8 years ago by hugoh

It looks like they're using:*

comment:8 Changed 8 years ago by pde

Okay, I've tried to commit a fix in git.

If you feel like it, you could test it as follows:

git clone
cd https-everywhere
git checkout 3.0
./ today
to install the CRX, you will have to go through the stupid obscure ritual that Chrome forces you through (click on the crx, open chrome:extensions, drag and drop the little popup at the bottom of the screen into the extensions tab). If that doesn't work for you, feel free to prod this bug.

comment:9 Changed 8 years ago by pde

sorry, that should be

comment:10 Changed 8 years ago by pde

Also note that if you install a custom build of HTTPS Everywhere for chrome, it will be signed with a different key, so it will be possible to install it at the same time as the official release. You should therefore go to the extensions tab and disable or delete the official version while you're testing a custom build.

comment:11 Changed 8 years ago by pde

Resolution: fixed
Status: assignedclosed

In any case this should be fixed in a new release shortly. If it isn't, please reopen.

Note: See TracTickets for help on using tickets.