-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remix should not rely on Response.headers.raw #4354
Remix should not rely on Response.headers.raw #4354
Comments
I think they did it at one point due to an error in how duplicate headers were being handled in Now that Remix uses its own fetch implementation, I think we should go back to |
This is causing problems when doing certain things with resource routes - e.g. handing GQL requests |
Closed by #7150 |
🤖 Hello there, We just published version Thanks! |
🤖 Hello there, We just published version Thanks! |
What version of Remix are you using?
1.7.2
Steps to Reproduce
Any
Response
object that is created through other means than@remix-run/node
(non node-fetch polyfills/undici/node builtins) fails here because Remix relies on the non standardReponse.headers.raw
:remix/packages/remix-express/server.ts
Lines 125 to 129 in e260b2b
Expected Behavior
Remix should use the standard
Response.headers
interface to maximize compatibility, eg:Actual Behavior
Handing off a
Response
to Remix results in an error:The text was updated successfully, but these errors were encountered: