| ... | ... | @@ -56,12 +56,6 @@ Sadly, no. Even if the file in question is stored inside of your cache, your bro |
|
|
|
|
|
|
|
Even if a resource is not locally available, Decentraleyes offers improved protection by stripping optional headers from intercepted CDN-requests. This keeps specific data, such as what page you are on, from reaching delivery networks. Whitelisting a domain does not affect this measure.
|
|
|
|
|
|
|
|
#### Why am I receiving HTTPS Everywhere-related warnings on Chrome or Chromium?
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
This means that it's safe to disable HTTPS Everywhere for supported CDNs, as long as you're using Decentraleyes v1.3.7.1 (or higher). Doing so should prevent any further related conflicts and warnings. Just follow 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?
|
|
|
|
|
|
|
|
Decentraleyes was designed to complement all kinds of other privacy-enhancing extensions including, but surely not limited to: Cookie AutoDelete, Disconnect, HTTPS Everywhere, NoScript Security Suite, Privacy Badger, RequestPolicy Continued, uBlock Origin, and uMatrix.
|
| ... | ... | |
