... | ... | @@ -56,6 +56,16 @@ Sadly, no. Even if the file in question is stored inside your cache, your browse |
|
|
|
|
|
If a resource cannot be fetched locally and Decentraleyes is instructed to allow requests for any missing resources (default behaviour), it will at least clear out the request's "Referer" HTTP header before sending it off to the Content Delivery Network in question.
|
|
|
|
|
|
##### Why am I receiving HTTPS Everywhere-related warnings on Chrome or Chromium?
|
|
|
|
|
|
This happens when both extensions are attempting to redirect a request, and only one of them (the most recently installed one) is winning the race. Decentraleyes v1.3.7.1 (and up), will _automatically_ set up secure connections when forced to let a given request through.
|
|
|
|
|
|
What this means, is that it's safe to disable HTTPS Everywhere _for any supported CDN_, as long as you're using a recent version of Decentraleyes. Doing so will prevent further conflicts.
|
|
|
|
|
|
![HTTPS Everywhere Fix](https://decentraleyes.org/d9d7515eb/https-everywhere-fix.png)
|
|
|
|
|
|
> _Simply untick the CDN in question, from the conflicting website, to disable it globally._
|
|
|
|
|
|
##### Will it work well in combination with other privacy enhancing add-ons?
|
|
|
|
|
|
Decentraleyes was designed to complement all sorts of other privacy enhancements including, but surely not limited to: BetterPrivacy, HTTPS Everywhere, NoScript Security Suite, Privacy Badger, RequestPolicy, Self-Destructing Cookies, uBlock Origin, and uMatrix.
|
... | ... | |