fix: properly merge headers in fetchWithEvent #980
+4
−4
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fixes nuxt/nuxt#31073 (will need backporting to v1 to actually fix though)
Currently, the merging behavior is inconsistent between useRequestFetch and client $fetch because of spreading headers without normalization. This PR fixes that by doing essentially same as what's done above in that file:
h3/src/utils/proxy.ts
Lines 37 to 42 in 0a796ff