Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Decentraleyes and HTTPZ (and other replacements for HTTPS Everywhere) #4

Open
Woofy-Wolf opened this issue Jan 12, 2019 · 2 comments
Open
Labels
question Further information is requested

Comments

@Woofy-Wolf
Copy link

Woofy-Wolf commented Jan 12, 2019

Hi claustromaniac,
Should I remove Decentraleyes if I want to use HTTPZ (or any other alternative to HTTPS Everywhere)? (I think the answer's yes but I'm not sure.) TIA.

@claustromaniac claustromaniac added the question Further information is requested label Jan 14, 2019
@claustromaniac
Copy link
Owner

claustromaniac commented Jan 14, 2019

Hi there,

HTTPZ should be fully compatible with Decentraleyes out of the box because it doesn't redirect sub-requests (only top-level document requests for now). I don't think there is any other way they can clash. I use both myself, by the way.

@Woofy-Wolf
Copy link
Author

Woofy-Wolf commented Jan 18, 2019

Thanks @claustromaniac. I think that an extension was intercepting requests to CDNs before Decentraleyes could re-direct those requests to its local resource. I removed and re-installed Decentraleyes, and the problem disappeared. I'm glad that HTTPZ was not the cause. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants