Fix: Contentful webhook body parse.

[anthonyshew]

Bug

• Related issues linked using fixes #number
• Integration tests added
• Errors have a helpful link attached, see contributing.md

Feature

• Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR.
• Related issues linked using fixes #number
• Integration tests added
• Documentation added
• Telemetry added. In case of a feature if it's used or not.
• Errors have a helpful link attached, see contributing.md

Documentation / Examples

• Make sure the linting passes by running pnpm lint
• The "examples guidelines" are followed from our contributing doc

[ijjk]

Is the content-type: application/json header not being sent with the Webhook request? If it is present it should already be parsing the req.body to JSON automatically.

x-ref:

next.js/packages/next/server/api-utils/node.ts

Line 170 in 4719517

if (type === 'application/json' || type === 'application/ld+json') {

[anthonyshew]

I didn't explicitly check headers but I've ran into this before with a webhook so I knew to try this pretty quickly. I can confirm that it goes from doesn't work to works with this change. 😬

I also quickly tried disabling bodyParser through export const config = { ... } to see if something else strange was going on but that also did not work as you'd expect.

I can go back and firm up the headers if needed!

[ijjk]

Ideally the content-type header is set from the Webhook although since we don't control it sounds alright to land

[mitul-s]

There’s a step in the README that tells you to update the header in Contentful to application/json

In other words, if you follow that then this is a breaking change. Spent a few hours today confused and trying to debug.

The README should be updated, or the PR should be reverted.

[ijjk]

Good catch, added a note to that section of the readme instead here #40925 as it's definitely favorable to use the correct content-type header.