Hype Machine doesn't support SSL, so rule breaks the site

https://hypem.com/

The site, by design, serves a lot of third-party content unencrypted, so it doesn't support SSL for mixed-content reasons. Ruleset should probably be rewritten to just exclude the site.

changed milestone to %HTTPS-E 3.2.3

added component::https everywhere/eff-https everywhere httpse-ruleset-bug milestone::HTTPS-E 3.2.3 owner::micahlee priority::medium resolution::fixed status::closed type::defect version::https-e 3.2.2 labels

Trac:
Owner: N/A to pde
Component: - Select a component to EFF-HTTPS Everywhere

Trac:
Status: new to assigned
Milestone: N/A to HTTPS-E 3.2.3
Version: N/A to HTTPS-E 3.2.2
Owner: pde to micahlee

Fixed in d122c11b

Trac:
Username: MB
Resolution: N/A to fixed
Status: assigned to closed

The commit that marked this 'resolved' doesn't actually address the Hype Machine (hypem.com) issue, fixes something else instead.

Can hypem.com be excluded from the list of services where HTTPS is forced?

I am the site administrator and because we currently use remote sources for audio playback (Soundcloud, Bandcamp, MP3 files) that are not on secure servers, as well as advertising that is not served securely, it is unlikely there is a way to make HTTPS Everywhere work with our site at this time.

If this changes, I am happy to even redirect to HTTPS on our own, as I am a big fan of EFF and the HTTPS-E project, but this is unfortunately not possible now.

Trac:
Username: fascinated
Status: closed to reopened
Resolution: fixed to N/A

Turned off in the 3.5 branch!

Trac:
Resolution: N/A to fixed
Status: reopened to closed

closed

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