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

..

fixtures

test: regenerate SSL certs

2025-12-15 08:45:47 +01:00

.eslintrc.json

refactor: prepare the migration to a monorepo

2024-07-08 11:02:37 +02:00

common.js

fix(eio): close HTTP requests with invalid content type

2026-04-27 11:08:50 +02:00

engine.io.js

chore: use prettier v3 everywhere (#5169)

2024-09-16 08:43:08 +02:00

middlewares.js

chore: use prettier v3 everywhere (#5169)

2024-09-16 08:43:08 +02:00

parser.js

chore: use prettier v3 everywhere (#5169)

2024-09-16 08:43:08 +02:00

server.js

fix(eio): close HTTP requests with invalid content type

2026-04-27 11:08:50 +02:00

util.mjs

refactor: prepare the migration to a monorepo

2024-07-08 11:02:37 +02:00

webtransport.mjs

fix(eio): prevent WebTransport connections when a middleware is registered

2026-04-16 10:19:34 +02:00