Custom Query (25166 matches)


Show under each result:

Results (88 - 90 of 25166)

Ticket Resolution Summary Owner Reporter
#5754 duplicate HTTPS Everywhere (Chrome) breaks MSDN MB cypherpunks

Browsing MSDN, page rendering can be corrupted. For example:

Disabling HTTPS Everywhere for MSDN fixes things.

Using Chrome 18 (Stable, Windows) and HTTPS Everywhere 2012.5.1

#5944 wontfix - cant login into forums MB war59312


Can't log-in to:

Reloads forever and ever and ever and ever, you get the point.

Disable the entry for it in https everywhere and no such issue.

Take Care,


#6279 fixed Rules: POF / Plenty Of Fish MB grarpamp

1) POF is made up of many more hosts than just (www.)?

  • Documented observed hosts, implemented compact form with *'s. (But see Excludes TODO in the case that POF again does not deploy HTTPS everywhere in the future.)

2) Fixed poor forms

  • unnecessary mapping from https to https with 's?'
  • unused non-backref '?:'
  • mapping www to the domain itself

3) POF is now returning 302 (to HTTP) for all HTTPS requests.

  • Therefore the current rules in git are moot and result in POF falling back via redirection loop to insecure HTTP.
  • POF is now completely unencrypted with no HTTPS capability at all (except for maybe their payment server). Users should be wary about their privacy, account, and financial integrity when using POF.

printf 'GET / HTTP/1.0\nHost:\n\n' \

| openssl s_client -connect -quiet 2>/dev/null

HTTP/1.1 302 Found Location: Server: Microsoft-IIS/7.5 X-Powered-By: ASP.NET

4) Due to all this, the attached replacement ruleset is disabled by default. It should be committed as notes for if/when POF moves to https in the future.

Note: See TracQuery for help on using queries.