Release `increase_websocket_message_size` for use on production

[danamajid]

I’m working on adding support to connecting to any arbitrary websocket chrome dev protocol server for @cloudflare/playwright (in draft cloudflare/playwright#59) but seeing errors when the incoming WS messages are above 1mb. For example:

WebSocket protocol error; protocolError.statusCode = 1009; protocolError.description = Message is too large: 2417523 > 1048576

fc77758 introduced the compatibility flag increase_websocket_message_size that increases this limit. But this flag is not deployable to prod: The compatibility flag increase_websocket_message_size is experimental and cannot yet be used in Workers deployed to Cloudflare.

Any plans to enable this on prod @andyjessop @penalosa? I understand the comment says This is not expected ever to be made available in production, as large messages are inefficient. but w/ browser automation in the AI age being even more important, pretty key to be able to control CDP from Workers. CDP messages can be huge when running automation on websites with a big DOM tree.

[nickfujita]

Would like to second this, as we have a different, but related use case. We are receiving base64 audio via websocket from a TTS provider and sometimes the base64 responses per audio chunk returned are larger than the current limit. Currently there aren't any setting to request smaller chunks from the provider, so we would need this limit to be increased.

For reference others on an unrelated platform had something similar where they just increased the limit on the message size.