Network limiter doesn't throttle websocket connections
Categories
(Core :: Networking: WebSockets, defect, P2)
Tracking
()
People
(Reporter: marsal2000, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [necko-triaged])
Steps to reproduce:
Open site with streaming through websocket instead of webrtc
Open Devtools
Navitage to Network
Enable Throttling
Actual results:
The network did not get throttled on the page, no matter the settings
Expected results:
The websocket traffic should've been throttled
Comment 1•5 months ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Networking: WebSockets' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Updated•5 months ago
|
Updated•5 months ago
|
Comment 2•5 months ago
|
||
@valentin - do you know how we're doing devtools throttling?
The thottling happens in devtools here.
While the initial channel to deal with the WS upgrade would be throttled, websocket channels might not.
I think we need additional work to support this for websockets.
With downloads, we probably need to change WebSocketChannel::OnInputStreamReady so we don't read more than allowed.
With uploads either WebSocketChannel::OnOutputStreamReady or WebSocketChannel::EnqueueOutgoingMessage
Comment 4•4 months ago
|
||
We might have a similar problem for WebTransport as well.
Updated•4 months ago
|
Description
•