We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The PROXY blackhole approach used in this repo has stopped working for HTTPS requests on all iOS after updating to Safari on iOS/iPadOS 15.
Most requests now are HTTPS, so this breaks functionality.
Safari 15 appears to bypass the proxy.pac PROXY and sends requests to https://unwarranted.tracker.website/?whatever.
I hypothesize the reason is that the proxy returns 400 for such HTTPS CONNECT requests. Its behavior, expected for HTTPS CONNECT requests,looks like:
curl -I --proxy http://my.blackhole.server:8119 https://unwarranted.tracker.website/?whatever HTTP/1.1 400 Bad Request Server: nginx/1.21.3 Date: Sat, 25 Sep 2021 19:17:07 GMT Content-Type: text/html Content-Length: 157 Connection: close curl: (56) Received HTTP code 400 from proxy after CONNECT
The fix appears to be to deprecate this repo and use Privoxy’s HTTPS inspection along with adblock2privoxy.
Reference: https://developer.apple.com/forums/thread/691279
The text was updated successfully, but these errors were encountered:
Add HTTPS Inspection, Deprecate squid and easylist-pac-privoxy
2e8d931
See: * essandess/easylist-pac-privoxy#21 * https://bugs.chromium.org/p/chromium/issues/detail?id=593759 * https://blog.checkpoint.com/2017/04/27/osx-malware-catching-wants-read-https-traffic/
No branches or pull requests
The PROXY blackhole approach used in this repo has stopped working for HTTPS requests on all iOS after updating to Safari on iOS/iPadOS 15.
Most requests now are HTTPS, so this breaks functionality.
Safari 15 appears to bypass the proxy.pac PROXY and sends requests to https://unwarranted.tracker.website/?whatever.
I hypothesize the reason is that the proxy returns 400 for such HTTPS CONNECT requests. Its behavior, expected for HTTPS CONNECT requests,looks like:
curl -I --proxy http://my.blackhole.server:8119 https://unwarranted.tracker.website/?whatever HTTP/1.1 400 Bad Request Server: nginx/1.21.3 Date: Sat, 25 Sep 2021 19:17:07 GMT Content-Type: text/html Content-Length: 157 Connection: close curl: (56) Received HTTP code 400 from proxy after CONNECT
The fix appears to be to deprecate this repo and use Privoxy’s HTTPS inspection along with adblock2privoxy.
Reference: https://developer.apple.com/forums/thread/691279
The text was updated successfully, but these errors were encountered: