Closed
Bug 618787
Opened 15 years ago
Closed 15 years ago
network.websocket.enabled true is broken
Categories
(Core :: Networking: WebSockets, defect)
Core
Networking: WebSockets
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.
Comment 2•15 years ago
|
||
did you try setting network.websocket.override-security-block?
| Reporter | ||
Comment 3•15 years ago
|
||
I did without success, did you?
| Reporter | ||
Comment 4•15 years ago
|
||
it was also set true as default...
another bug?
| Reporter | ||
Comment 5•15 years ago
|
||
oops..
well something worked!
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → WORKSFORME
| Reporter | ||
Comment 6•15 years ago
|
||
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 → ---
| Reporter | ||
Comment 7•15 years ago
|
||
well probably this bug has morphed,
Status: REOPENED → RESOLVED
Closed: 15 years ago → 15 years ago
Resolution: --- → WORKSFORME
Comment 8•15 years ago
|
||
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.
Description
•