fix: Ensure cookies set in middleware are available on initial render #851
+61
−9
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.
For #850
We should remove
x-middleware-set-cookie
fromfilteredHeaders
. Instead we remove it on theoverwrittenResponseHeaders
which will be passed to the response.reqProps
inrequestHandler.ts
will use the originalheaders
object, and pass it intoprocessRequest
. This makes sure we will see the header on initial render when usingcookies().get()
from Next.