Damien Arrachequesne fc11285e14 fix(eio): close HTTP requests with invalid content type
Before this commit, after the initial handshake, an HTTP request with a "application/octet-stream"
content type would trigger a "invalid content" error at the Engine.IO level, but would not be
properly closed, which could possibly lead to resource exhaustion.

This behavior was introduced in [1] (engine.io@4.1.0, January 2021).

[1]: 663d326d18
2026-04-27 11:08:50 +02:00
2026-04-02 17:40:35 +02:00
2025-12-15 08:55:26 +01:00
2024-07-09 10:44:20 +02:00
2025-12-22 13:45:36 +01:00
2024-07-08 16:07:34 +02:00
2026-03-18 09:09:12 +01:00

socket.io

Latest NPM version Build status Downloads per month

Getting Started

Please check our documentation here.

Questions

Our issues list is exclusively reserved for bug reports and feature requests. For usage questions, please use the following resources:

Security

If you think that you have found a security vulnerability in our project, please do not create an issue in this GitHub repository, but rather refer to our Security Policy.

Issues and contribution

Please make sure to read our Contributing Guide before creating an issue or making a pull request.

Thanks to everyone who has already contributed to Socket.IO!

License

MIT

Description
No description provided
Readme MIT 43 MiB
Languages
TypeScript 63.8%
JavaScript 36%