Request blocking does not block websocket requests
Reported by
arag...@gmail.com,
Apr 20 2018
|
|||||||
Issue description
Chrome Version : 66.0.3359.81
OS Version: OS X 10.13.3
URLs (if applicable) : any ws:///
Other browsers tested:
Add OK or FAIL after other browsers where you have tested this issue:
Safari: does not offer request blocking as a dev feature
Firefox: does not offer request blocking as a dev feature
IE/Edge: no idea
What steps will reproduce the problem?
1. open a page that opens a websocket connection
2. add the relevant ws url to the request blocking dev tool
3. reload the page
What is the expected result?
The request is blocked
What happens instead of that?
The request happily goes on like nothing happened
Please provide any additional information below. Attach a screenshot if
possible.
UserAgentString: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.81 Safari/537.36
,
Apr 20 2018
Removing network label and adding loader. I think this should be implementable entirely in the render process.
,
Apr 23 2018
,
Apr 26 2018
,
Apr 27 2018
This is probably best implemented as a blink::WebSocketHandshakeThrottle, probably chaining back to the existing throttle (ie. WebSocketSBHandshakeThrottle).
,
Jun 11 2018
,
Oct 12
|
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by ellyjo...@chromium.org
, Apr 20 2018Status: Untriaged (was: Unconfirmed)