Closed r34son closed 4 months ago
Here resHeaders
contain location
key. It's strange that you get location
header and assign it to Location
key.
I can open a PR that fixes this behavior, if you approve that it's real issue.
Clients and servers are suppose to handle either casing right? But in general, they should be pascal casing. Can you figure out where/what is setting it to the lower case location
and fix that? If that's somewhere upstream, then we should delete it from the resHeaders
to remove the duplication.
It breaks app, because by design 2 same http headers are combined in one, values in which are separated by commas. https://www.rfc-editor.org/rfc/rfc9110.html#name-field-lines-and-combined-fi
Also realised that header names are lowercase in https://developer.mozilla.org/en-US/docs/Web/API/Headers
I'll open pr that changes Location
to location
.
I'm using
next-intl
. Server function handles redirect from middleware, but there is an issue that it duplicateslocation
header because of case mismatch.