Releases: websockets/ws
Releases · websockets/ws
6.1.4
16 Feb 17:04
Compare
Sorry, something went wrong.
No results found
Bug fixes
Fixed an issue that caused the Host
header to always include a port (#1510 ).
6.1.3
24 Jan 07:06
Compare
Sorry, something went wrong.
No results found
Bug fixes
Fixed a bug that, under certain circumstances, prevented the close frame from
being parsed (#1494 ).
6.1.2
17 Nov 20:07
Compare
Sorry, something went wrong.
No results found
Bug fixes
Restored compatibility with Node.js < 6.13.0 (26436e0 ).
6.1.1
17 Nov 07:10
Compare
Sorry, something went wrong.
No results found
Bug fixes
Queued messages to send are now discarded if the permessage-deflate is enabled
and the socket closes prematurely (#1464 , #1471 ).
6.1.0
05 Oct 06:50
Compare
Sorry, something went wrong.
No results found
Features
The WebSocket server now emits a 'close'
event when the server
closes (#1453 ).
6.0.0
21 Jul 13:34
Compare
Sorry, something went wrong.
No results found
Breaking changes
Dropped support for Node.js 4 (d73885c ).
Added a shim that throws an error when used if the package is bundled for the
browser (#1345 ).
Added a maxPayload
option on the client. Defaults to 100 MiB (#1402 ).
Dropped support for the memLevel
and level
options. Use
zlibDeflateOptions
instead. (80e2002 ).
5.2.2
11 Jul 19:51
Compare
Sorry, something went wrong.
No results found
5.2.1
23 Jun 16:02
Compare
Sorry, something went wrong.
No results found
Bug fixes
Fixed a bug that could prevent buffered data from being processed under
certain circumstances (6046a28 ).
5.2.0
21 May 19:16
Compare
Sorry, something went wrong.
No results found
Features
Added ability to specify custom headers when rejecting the handshake (#1379 ).
5.1.1
02 Apr 13:21
Compare
Sorry, something went wrong.
No results found
You can’t perform that action at this time.