Opened 9 years ago

Closed 9 years ago

#4399 closed defect (fixed) shouldnt be forced to https by HTTPS Everywhere

Reported by: Getty Owned by: pde
Priority: Medium Milestone:
Component: HTTPS Everywhere/EFF-HTTPS Everywhere Version:
Severity: Keywords:
Cc: torsten@… Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


We on DuckDuckGo added a new helpsite on it is not proper reachable via which gives us right now bug reports, a user gave us this hint to solve it which is probably right, sadly i dont use HTTPS Everywhere and can't tell. Would it be possible that we fix this situation and gets not forced to https?

Thanks in advance :)

Child Tickets

Change History (3)

comment:1 Changed 9 years ago by Getty

Cc: torsten@… added

comment:2 Changed 9 years ago by Anna

I've been trying to learn rulesets and as I understand it, that sort of problem should just need an exclusion line added in the site rule so I was going to give it a shot but there's something strange going on here that I don't really understand. Here's what I found trying to recreate the problem:

  1. When I visit the help page which appears to be http, the browser and Perspectives both register a certificate for * (which looks like the website support company and the page loads a couple of images from them, possibly more) and neither the browser nor Perspectives likes that certificate. If that's the problem the user is encountering, that's not a problem with https-everywhere.

  1. Beyond the security certificate problem, the addon doesn't appear to attempt to forward me to https and when I type https manually, it manages to forward me to http without a redirect loop and I can access the content just fine.

comment:3 Changed 9 years ago by pde

Resolution: fixed
Status: newclosed

Fixed in git master and stable:

Releases coming soon.

Note: See TracTickets for help on using tickets.