Closed Bug 618787 Opened 15 years ago Closed 15 years ago

network.websocket.enabled true is broken

Categories

(Core :: Networking: WebSockets, defect)

defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: jay, Unassigned)

Details

provide means through about:config to enable websockets #616733 disabled websockets. blizzard and others suggest a means to enable will be provided. about:config network.websocket.enabled true remains default but does not enable websockets. parity Opera enable websockets, tick box default unticked.
4.0b8pre 2010-12-12
Version: unspecified → Trunk
did you try setting network.websocket.override-security-block?
I did without success, did you?
it was also set true as default... another bug?
oops.. well something worked!
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → WORKSFORME
so seems set network.websocket.enabled true network.websocket.override-security-block true then restart mozilla, not quite as simple as Opera's tick box... why have both? just set enabled false as default, with warning if necessary.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
well probably this bug has morphed,
Status: REOPENED → RESOLVED
Closed: 15 years ago15 years ago
Resolution: --- → WORKSFORME
Let's say you deliberately set network.websocket.enabled to false and we then made the default value false. So far so good. When the dangerous security holes in the protocol are fixed we want to enable it again so we set the flag to true by default and websockets are silently reenabled for you even though you stated specifically previously you didn't want them.
You need to log in before you can comment on or make changes to this bug.