Open Bug 1889891 Opened 3 months ago Updated 1 month ago

Network monitor offline mode doesn't block messages over active websocket connection

Categories

(Core :: Networking: WebSockets, defect, P2)

Product:
Core
Component:
Networking: WebSockets
Version:
Firefox 124
Type:
defect
Points:
5

Tracking

()

Status:
UNCONFIRMED

People

(Reporter: tlepel+bugzilla, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [necko-triaged][necko-priority-next])

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:124.0) Gecko/20100101 Firefox/124.0

Steps to reproduce:

  1. Open a website which starts a websocket connection with a server (in my case on localhost) and sends ping messages every few seconds.
  2. Open the network monitor in the developers tools and set the network throttling to 'offline'

Actual results:

The websocket messages are still being sent and received

Expected results:

The websocket should close because of a broken link to the server and messages should not be sent or received successfully

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.

Component: Untriaged → Networking: WebSockets
Product: Firefox → Core

This is another version of bug 1880534. I think it might be easier to implement than full throttling.

Blocks: necko-devtools
Severity: -- → S3
Priority: -- → P2
See Also: → 1880534
Whiteboard: [necko-triaged][necko-priority-next]
Points: --- → 5
You need to log in before you can comment on or make changes to this bug.