You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A /ws endpoint that provides a basic WebSockets-based echo server would be a useful addition, if it's not too difficult to implement without pulling in any external dependencies. MDN's guide to writing a WebSocket server might be a good starting point.
This would be very useful to help test HTTP proxies to ensure that they correctly support WebSockets, similar to the SSE endpoint proposed in #150.
Here we add a new `/websocket/echo` endpoint, which implements a basic
WebSocket echo service.
The endpoint is powered by our own basic, zero-dependency WebSocket
implementation, which passes _almost_ every test in the invaluable
[Autobahn Testsuite](https://github.com/crossbario/autobahn-testsuite)
"fuzzingclient" set of integration tests, which will be run
automatically as part of our continuous integration tests going forward.
Closes#151.
A
/ws
endpoint that provides a basic WebSockets-based echo server would be a useful addition, if it's not too difficult to implement without pulling in any external dependencies. MDN's guide to writing a WebSocket server might be a good starting point.This would be very useful to help test HTTP proxies to ensure that they correctly support WebSockets, similar to the SSE endpoint proposed in #150.
We could potentially leverage something like https://github.com/crossbario/autobahn-testsuite to verify the basic functionality of the implementation, ideally wired up into our CI test suite.
The text was updated successfully, but these errors were encountered: