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
wildcards don't seem to work in the exclusions list #7
Comments
The wildcard exclusion behavior is not exposed to end users by (current) design for three debatable reasons:
Ah, thanks, I will fix this :) It is a quirk from where it was the case. I then removed this behavior when the project was not yet published as I thought that it would then be trivial for websites to trigger this behavior and get excluded. |
That's a great point. If this became widespread, the effectiveness of Privaxy could evaporate. Perhaps a good compromise would be to add handshake error domains into a checkbox list in the UI, so that it's quick and easy to add them as exclusions if that's what the user wants. In this case, a total of 5 dropbox.com and dropboxapi.com domains were getting handshake errors (all from the MacOS client, not from visiting the website). |
I fixed the explanatory text in d2bfaeb. |
I've tried both *.dropbox.com and just dropbox.com, and in both cases subdomains continue to generate TLS handshake errors in the log. Adding each offending subdomain fixes it.
I also noticed that the UI says that domains that have handshake failures will be automatically added to the exclusion list, but that doesn't seem to be happening in my case.
Context: MacOS, pre-built binary
The text was updated successfully, but these errors were encountered: