Kthat would be ideal
Kit sounds broken, but I'd need to see the complete code to be sure. It vaguely sounds like a bad interaction with output gates, as described in the blog post that was just posted. But output gates should only apply when storage operations are used...
Kyeah if you don't do any storage ops, then output gates shouldn't be kicking in. Something else is wrong.
Konly in DO, or does the same apply in a stateless worker?
KHmm, I think this might be because Cloudflare buffers POST requests in general. (Not even specific to Workers.)
K(or any kind of request body)
KI think it'll just give you an error after like 100MB
Kuploading 1GB works?
KI guess I'm not sure what the limit is. This isn't actually part of Workers, I don't know much about how it works. But I know that request bodies are buffered and only delivered once the whole body is uploaded. I don't think you can turn it off, unfortunately.
Kcan you possibly get the client to use a WebSocket?
Kdoh
KI've heard of enterprise customers turning off buffering. I don't understand why it isn't just an option in the dashboard.
Kmaybe file a support request, see what they say
Kthat's unrelated to buffering
KYeah that's response buffering, which isn't what you care about. Request buffering is the problem here.
K(and response buffering is off by default, but request buffering is on by default)