DELETE requests add a "Content-Length: 0" header, causing undici to error "Request body length does not match content-length header"

[dan-hammond]

DELETE requests add a "Content-Length: 0" header, causing undici to error "Request body length does not match content-length header"

[brc-dd]

undici fixed this in nodejs/undici#2046 , but not sure if it'll be backported to LTS. I'm using nitro.experimental.nodeFetchCompat till that fix makes to a node LTS 👀

[wug-ge]

I'm facing the same issue using Nuxt,js routeRules proxy and my DELETE requests don't work.

Putting

delete opts.fetchOptions.headers['content-length']

before this line

https://github.com/unjs/h3/blob/12ccb81432a62783fe951a8170976c8162bce44a/src/utils/proxy.ts#L77

solves my issue, otherwise it fails with a UND_ERR_REQ_CONTENT_LENGTH_MISMATCH.

I'm haven't digged deep enough into the ecosystem to understand fully what's going on, I'd really appreciate if someone could explain further what exactly is happening / provide a workaround.

For now I might have to use a different proxy.

If wanted, I'm happy to do some digging myself. (not sure how efficient I'll be here though)

[brc-dd]

You might also need to disable built-in fetch. I'm using this kind of setup:

// package.json

  "scripts": {
    "dev": "pnpm nuxt dev",
    "build": "pnpm nuxt build",
    "generate": "pnpm nuxt generate",
    "preview": "pnpm nuxt preview",
    "postinstall": "pnpm nuxt prepare",
    "nuxt": "NODE_OPTIONS='--no-experimental-fetch' nuxt"
  }

// nuxt.config.ts

export default defineNuxtConfig({
  nitro: {
    experimental: {
      nodeFetchCompat: true
    }
  }
})

At the time I posted that comment, it was working fine just by setting in nuxt.config, but broke between some Nuxt minor IG. So you might need to add both. I have confirmed that it works fine in latest Node.js without any extra config, so probably this issue can be closed as I think this was always an upstream issue.

PS: I just read [email protected] release notes and looks like it should now work fine on latest LTS too. 🎉

[pi0]

Thanks for the issue. Related upstream issues http-party/node-http-proxy#1343 and nodejs/node#27880

This feature was originally introduced in http-proxy via http-party/node-http-proxy#742 as part of bug fix for nginx and chunked streaming. I will have to check it more in defails.

Anyway i think it is a valid bug if we are overriding the existing content-length.

[wug-ge]

@brc-dd can you explain what you mean by using nitro.experimental.nodeFetchCompat?

I can't find much about it, what it is and how do I set it in my Nuxt config? 😄

I tested this issue with node 18, 20 and 21 and it persists in all versions. My current workaround is to add something random in the body of the DELETE request, which is quiet ugly...

[Denoder]

@wug-ge

export default defineNuxtConfig({
    nitro: {
        experimental: {
            nodeFetchCompat: true
        }
    }
})