... | ... | @@ -60,11 +60,7 @@ If a resource cannot be fetched locally and Decentraleyes is instructed to allow |
|
|
|
|
|
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 **un**tick the CDN in question, from the conflicting website, to disable it globally._
|
|
|
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. Follow [this short guide](https://decentraleyes.org/configure-https-everywhere/) to properly configure your installation of HTTPS Everywhere.
|
|
|
|
|
|
##### Will it work well in combination with other privacy enhancing add-ons?
|
|
|
|
... | ... | |