Closed Bug 1313189 Opened 9 years ago Closed 3 years ago

WebSockets take a long time to connect with no internet connection

Categories

(Core Graveyard :: DOM: Flyweb, defect)

Product:
Core Graveyard
Component:
DOM: Flyweb
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED INCOMPLETE

People

(Reporter: squib, Unassigned)

Details

If you have a FlyWeb server that uses a WebSocket and you run it on a network with no internet connection, it takes a long time (20 seconds) for clients to actually get a functional WebSocket to the server. You can see this in the following demo app, which just creates a FlyWeb server and a WebSocket connection: <https://github.com/jimporter/flywebrtc/tree/websocket-delay>. I tested this out by just unplugging my router from my modem and watching the console log. I'm not sure if this is actually a bug in WebSockets or FlyWeb itself though.
Product: Toolkit → Core
Product: Core → Core Graveyard

This bug lies at rest in the graveyard.

Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.