1MiB size limit for received websocket messages
I have an API running on workers which gets some data from a websocket. Some received messages contain base64 encoded data that's over the 1MiB limit (on average ~1.4MiB). I haven't found any way to work around this limit (afaik reading one message in chunks is not possible). I can't control anything about how the wss sends these messages, and I know that messages larger than 1MiB are probably not that common for most users but I'm just wondering if any workaround is even possible. Thanks!
0 Replies