fix: Forwarded event fetch request having double headers in Nuxt/SEO module (triggered in server middleware)

[Xenossolitarius]

🐛 The bug

If you have a server middleware in the latest version of H3. and using sitemaps this triggers the error and it breaks.
I think this is a H3 upstream issue but I will open it here too for visibility.
Check bottom issue. It's a bit too much for me to fix. I've just ignored the '/api' routes for now but not everybody can do it.

unjs/h3#956

🛠️ To reproduce

http://easy-to-reproduce.com

🌈 Expected behavior

No errors

ℹ️ Additional context

No response

[Applelo]

For people looking for a temporary fix, put this into your package.json and run pnpm install

"pnpm": {
    "overrides": {
      "h3": "1.13.0"
    }
  }

[Xenossolitarius]

The cause of the issue is maybe downstream. It all depends on which package owner decides who wnats to fix it. Either we send host header in lowercase or h3 merges these headers differently. One of the workarounds is to just ignore sitemap fetches in nuxt/nitro middleware

[harlan-zw]

Happy to lowercase 👍 Have pushed up a release with that.