gecko-dev/remote/server
Henrik Skupin 96a354322c Bug 1721148 - [remote] Report WebSocket handshake failures to the client. r=webdriver-reviewers,jgraham
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
2021-07-23 16:12:32 +00:00
..
README
WebSocketHandshake.jsm Bug 1721148 - [remote] Report WebSocket handshake failures to the client. r=webdriver-reviewers,jgraham 2021-07-23 16:12:32 +00:00
WebSocketTransport.jsm Bug 1601618 - [remote] Use lazy loading of modules and delayed setting of global properties. r=remote-protocol-reviewers,jdescottes 2021-02-26 15:37:41 +00:00

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

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 wed like to move away from using
any of this code.