Releases: websockets/ws
Releases Β· websockets/ws
8.8.1
Bug fixes
- The
Authorization
and Cookie
headers are no longer sent if the original
request for the opening handshake is sent to an IPC server and the client is
redirected to another IPC server (bc8bd34).
8.8.0
Features
- Added the
WS_NO_BUFFER_UTIL
and WS_NO_UTF_8_VALIDATE
environment
variables (becf237).
8.7.0
Features
- Added the ability to inspect the invalid handshake requests and respond to
them with a custom HTTP response. (6e5a5ce).
Bug fixes
- The handshake is now aborted if the
Upgrade
header field value in the HTTP
response is not a case-insensitive match for the value "websocket" (0fdcc0a).
- The
Authorization
and Cookie
headers are no longer sent when following an
insecure redirect (wss: to ws:) to the same host (d68ba9e).
8.6.0
Features
- Added the ability to remove confidential headers on a per-redirect basis (#2030).
8.5.0
Features
- Added the ability to use a custom
WebSocket
class on the server (#2007).
Bug fixes
- When following redirects, the
Authorization
and Cookie
headers are no
longer sent if the redirect host is different from the original host (#2013).
8.4.2
Bug fixes
- Fixed a data framing issue introduced in version 8.4.1 (#2004).
8.4.1
Notable changes
- To improve performance, strings sent via
websocket.ping()
,
websocket.pong()
, and websocket.send()
are no longer converted to
Buffer
s if the data does not need to be masked (#2000).