Note that this this only intercepts websocket requests in the DOM window context. It could be potentially be bypassed by using workers which have access to websocket APIs.
The real solution is for chrome to add support to their request filtering.
Filters such as `*$websocket`[1] should also work in workers as well, since such filter syntax causes a CSP directive to forbid websocket connections to be injected into a page.
The real solution is for chrome to add support to their request filtering.