-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
websocket blocked when easylist match #1943
Comments
Will release 1.9.4 ASAP. |
Issue was that any match was considered when evaluating whether websocket should be wholly block or not. For the purpose of injecting a websocket-blocking CSP, only filters with an explicit websocket option must be considered. |
What about the easylist filters:
any chance to be "seen" / converted by ubo ? |
Good idea. I didn't even know these filters existed. Probably could be converted at compile time, with a special code path. The ones with |
@gorhill FYI here are the ws/wss filters I found in Easylist & Easyprivacy |
I wish Essentially this means that |
I understand your worries. Maybe @ryanbr could tell us why |
on extratorrent.cc in ubo I can see this url (..ubofix) in network tab (and it seems also blocked but a user reported ads):
|
Site is down, "503 Service Unavailable". The ubofix URL is a fake, internal-only one, emitted by uBO-WebSocket and caught by uBO and never leaves the browser. I should probably convert to using postMessage() as suggested here. |
Read first: https://github.com/gorhill/uBlock/blob/master/CONTRIBUTING.md
Describe the issue
i'm developing a JS app which tries to use a websocket (socket.io) on the local domain.
however the request to wss://localhost:8080 gets blocked when the URI of the page has an easylist match:
script console says:
bundle.js:46 Refused to connect to 'wss://localhost:8080/socket.io/?EIO=3&transport=websocket&sid=4nqaF7ANnFB8df04AAAa' because it violates the following Content Security Policy directive: "connect-src http:".
i'd expect the connection to wss:// or ws:// to be allowed for the same host and port.
Your settings
settings backup txt
Default filter lists + DEU
Your custom filters (if any)
The text was updated successfully, but these errors were encountered: