Hi all!
Before creating an issue, I wanted to discuss the following: aiohttp has no limit on websocket message sizes.
That looks pretty dangerous, as it allows to DoS/OOM the server with a single client without any effort at all.
Closest 'conceptual' relative of aiohttp (IMHO) aka tornado has this limit both on client and on server APIs:
It cannot be implemented on the application layer - it's too late, message has been fully loaded already. This limit must be deep in protocol implementation, where websocket fragmented messages are collected.
Am I missing smth?
ps. I understand that it can probably solved using a production reverse proxy, but for pure WS workload direct connection seems reasonable too.