... | ... | @@ -58,9 +58,9 @@ If a resource cannot be fetched locally and Decentraleyes is instructed to allow |
|
|
|
|
|
##### 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.
|
|
|
They show up when both extensions are attempting to redirect a specific request. The race is always won by the most recently installed extension. This is why recent versions of Decentraleyes automatically set up secure connections when forced to let intercepted requests through.
|
|
|
|
|
|
What this means, is that it's safe to disable HTTPS Everywhere _for supported CDNs_, 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.
|
|
|
This means that it's safe to disable HTTPS Everywhere for supported CDNs, as long as you're using a recent version of Decentraleyes _(1.3.7.1 and up)_. Doing so should prevent further warnings and conflicts. Follow this [this short guide](https://decentraleyes.org/configure-https-everywhere/) to configure your installation of HTTPS Everywhere.
|
|
|
|
|
|
##### Will it work well in combination with other privacy enhancing add-ons?
|
|
|
|
... | ... | |