Does anyone account this error(content-length mismatch)?

[ReginaLiang]

I used the nextjs, then fetch api, will occur Request body length does not match content-length header.
How to fix it?

Thanks.

[bnusunny]

@ReginaLiang Could you provide more details about how this error happened? The runtime version, the LWA version, the invoke mode, and how frequent did it happen?

[ReginaLiang]

@ReginaLiang Could you provide more details about how this error happened? The runtime version, the LWA version, the invoke mode, and how frequent did it happen?

Sure, I used lambda to deploy a nextjs app, and the runtime version is Nodejs 18, the LWA version is 0.8.4. Then there is an api gateway http api to call this lambda. HTTP API sets up a proxy for all requests. Finally, Nextjs application can run successfully, But when fetching the background API, it will report Request body length does not match content-length header. This problem only occurs in get requests, Post requests are fine. Can you provide some useful information? Many thanks!!!

[bnusunny]

@ReginaLiang can you provide more CloudWatch Logs related to the error message?

[ReginaLiang]

@ReginaLiang can you provide more CloudWatch Logs related to the error message?

FYI, This error is from Lambda. Thanks.

[bnusunny]

From these logs, it seems the next.js app was trying to send a GET request to another API and failed with the error Request body length does not match content-length header. Could you log the actual body lenthg and the content-length header before sending the request? Does this work on you local computer?

[ReginaLiang]

From these logs, it seems the next.js app was trying to send a GET request to another API and failed with the error Request body length does not match content-length header. Could you log the actual body lenthg and the content-length header before sending the request? Does this work on you local computer?

Yes, It works fine on my local computer. and the body as follows:

[bnusunny]

This is the Lambda payload. LWA will translate it into a HTTP request and send to your next.js web app. Could you add debug logging in your next.js web app to show the http request it received? Especially the content-length header and the actual body.

[ReginaLiang]

This is the Lambda payload. LWA will translate it into a HTTP request and send to your next.js web app. Could you add debug logging in your next.js web app to show the http request it received? Especially the content-length header and the actual body.

In fact, my nextjs app does not receive any parameters from lambda, but simply requests other apis through fetch, Will this have an impact?

[bnusunny]

Hmm, this doesn't seem like an issue with LWA. Could you share a simple example which can reproduce this issue?

[ReginaLiang]

Hmm, this doesn't seem like an issue with LWA. Could you share a simple example which can reproduce this issue?

I will prepare a sample to reproduce this problem in my free time. I appreciate your help.