mirror of
https://github.com/mozilla/gecko-dev.git
synced 2024-12-03 02:25:34 +00:00
96a354322c
When a WebSocket upgrade fails we currently do not send any details of the error. As such it makes it hard to figure out the real underlying issue. Further some clients like curl are hanging and do not immediately exit when the response has been received. Specifying the Content-Length header within the response fixes it. Differential Revision: https://phabricator.services.mozilla.com/D120575 |
||
---|---|---|
.. | ||
README | ||
WebSocketHandshake.jsm | ||
WebSocketTransport.jsm |
These files provide functionality for serving and responding to HTTP
requests, and handling WebSocket connections. For this we rely on
httpd.js and the chrome-only WebSocket.createServerWebSocket function.
Generally speaking, this is all held together with a piece of string.
It is a known problem that we do not have a high-quality HTTPD
implementation in central, and we’d like to move away from using
any of this code.