fix: overhaul headers proxy#1937
Closed
huseeiin wants to merge 4 commits intosolidjs:mainfrom
huseeiin:headers-feature
Closed
fix: overhaul headers proxy#1937huseeiin wants to merge 4 commits intosolidjs:mainfrom huseeiin:headers-feature
huseeiin wants to merge 4 commits intosolidjs:mainfrom
huseeiin:headers-feature
Conversation
🦋 Changeset detectedLatest commit: c2bfa86 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
✅ Deploy Preview for solid-start-landing-page ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
2 tasks
More templates
commit: |
Contributor
Author
|
don't merge this, its stupid. after h3 v2 we will get a proper response Headers |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
this fixes many issues with the original headers proxy, for example, now:
getRequestEvent().response.headers.toString()returns "[object Headers]" instead of "[object Object]"getRequestEvent().response.headers instanceof Headerswill returntrueand so on, because we're now using a native
HeadersobjectPlease check if your PR fulfills the following requirements:
What is the current behavior?
What is the new behavior?
Other information