fix(cloudflare): pass raw body instead of parsing it

[brendonmatos]

🔗 Linked issue

❓ Type of change

• 📖 Documentation (updates to the documentation or readme)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

In cases where it is necessary to read the body of the raw request, the cloudflare deploy was always parsing the body even using useRawBody.
Implementations like the stripe's webhook that needs to read the raw body would break.

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[pi0]

Hi @brendonmatos. Thanks for PR. Would you please provide a reproduction or a better example? We might fix the useRequestBody utility instead as it respects the mime type to support blob and formdata as well (.txt() only works for text and json)

[brendonmatos]

In my case the useRequestBody was doing its job correctly.

The useRawBody returns the parsed body instead of raw when the localCall is invoked with the parsed body (it wasn't clear to me how or why this happens).
https://github.com/unjs/nitro/blob/9a799c921e3ed4db3245df186599062757d5f058/src/runtime/entries/cloudflare.ts#L25-L34

To support blobs and formdata an option can be to pass the buffer forward using cloudflare's event.request.arrayBuffer() and converting to buffer, like this:

body = Buffer.from(await event.request.arrayBuffer())

@pi0 What do you think about this?

[pi0]

Buffer for workers is supported via lots of unenv polyfills. If possible, it would be better to use arrayBuffer directly and handle it from h3 utility. (We already depend on Buffer.concat here)

Seems a good idea!

[brendonmatos]

thanks for the path you gave me!
the behaviour was implemented in both entries

[barisbora]

Can we pass CF records too?

https://developers.cloudflare.com/workers/runtime-apis/request/#incomingrequestcfproperties

[pi0]

Thanks!

[pi0]

Can we pass CF records too?

Another enhancement, but sure we shall pass them to event.context.cf