Luigi Pinca eeb76d313e [security] Fix crash when the Upgrade header cannot be read (#2231) ...

It is possible that the Upgrade header is correctly received and handled
(the `'upgrade'` event is emitted) without its value being returned to
the user. This can happen if the number of received headers exceed the
`server.maxHeadersCount` or `request.maxHeadersCount` threshold. In this
case `incomingMessage.headers.upgrade` may not be set.

Handle the case correctly and abort the handshake.

Fixes #2230

2024-06-16 15:20:07 +02:00

..

buffer-util.js

[minor] Move all buffer conversion functions to the buffer-util module

2019-03-02 18:55:16 +01:00

constants.js

[major] Drop support for Node.js < 4.5.0 (#1313)

2018-03-04 13:36:53 +01:00

event-target.js

[lint] Use prettier

2018-11-17 09:39:58 +01:00

extension.js

[lint] Use prettier

2018-11-17 09:39:58 +01:00

permessage-deflate.js

[minor] Refactor PerMessageDeflate.prototype.cleanup()

2018-12-24 15:16:54 +01:00

receiver.js

[minor] Move all buffer conversion functions to the buffer-util module

2019-03-02 18:55:16 +01:00

sender.js

[minor] Remove length threshold

2019-03-15 17:47:51 +01:00

validation.js

[lint] Use prettier

2018-11-17 09:39:58 +01:00

websocket-server.js

[security] Fix crash when the Upgrade header cannot be read (#2231)

2024-06-16 15:20:07 +02:00

websocket.js

[fix] Make WebSocket#close() set the close timer immediately

2019-03-26 18:23:27 +01:00