Response body ends prematurely

[ronag]

Haven't had time to check but I suspect we might have a problem with body sizes larger than 31 bit.

undici will complete without error before reading entire response body.

[ronag]

@dnlup would you mind taking a look and maybe making a test?

[mcollina]

How does Node.js handle this case?

[ronag]

It just works. This might be a wasm thing.

[dnlup]

Are we talking about something greater than Number.MAX_SAFE_INTEGER?

[ronag]

Are we talking about something greater than Number.MAX_SAFE_INTEGER?

No, I have a case where I'm unable to receive anything larger than ~2^31. I'm not sure if it's undici at the moment but I think it's good idea to have a test where we transfer more than 2^32 bytes.

[ronag]

Could also be a problem with Node 16 http1/http2 server. I'm seeing the issue in a reverse proxy in production.

[dnlup]

Inspecting llhttp I see content-length is an unsigned int of 64 bits. That should exclude some issues in the parser native side.

[dnlup]

I think the problem is with Node. It happens only if you pass the entire buffer to res.write. Undici errors with message The other side closed.

I used Node 16 to test.

[ronag]

Something is weird. undici always prematurely ends response at 1605405800 bytes without error. While curl properly reads all 5 GB.

[ronag]

@mcollina @dnlup

This fails: #805