useFetch will be http 400 when navigate from different layout page in old browser and ios app(alipay/qq)

[BluesYoung-web]

Environment

---

• Operating System: Linux
• Node Version: v20.9.0
• Nuxt Version: 3.12.2
• CLI Version: 3.12.0
• Nitro Version: 2.9.6
• Package Manager: npm@10.1.0
• Builder: -
• User Config: devtools, app, modules, legacy, experimental
• Runtime Modules: nuxt-vite-legacy@1.2.0
• Build Modules: -

---

Reproduction

https://stackblitz.com/edit/github-tphpdd?file=nuxt.config.ts

Describe the bug

When this issue (#24229) was closed, i have try the latest version.

I'm trying to polyfill the old browser(use nuxt-vite-legacy, my old browser is android chrome 56), but found an another bug:

'when navigate to a page which use different layout, useFetch's result will be http 400; but it will be ok when i refresh the page'

And then i test in ios alipay to valid if #24229 fixed, i found http 400 occur again. so, i guess it exsists in ios qq too.

Additional context

ScreenRecord_2024-06-17-10-40-51.mp4

my operate just like this.

Logs

No response

Tasks

Beta Give feedback

No tasks being tracked yet.

[stackblitz]

Start a new pull request in StackBlitz Codeflow.

• github-tphpdd (Open reproduction)

[danielroe]

In that case, you may need to set responseType: 'json' as one of the options to useFetch. Does that help?

[BluesYoung-web]

In that case, you may need to set responseType: 'json' as one of the options to useFetch. Does that help?

nop! it dosen't work, still http 400

[danielroe]

Is there a way to test this on a computer?

[BluesYoung-web]

Is there a way to test this on a computer?

I just try chrome56 on windows, it occur too.

You can download this version's chrome form here