-
Notifications
You must be signed in to change notification settings - Fork 30
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
Request header unexpectedly mutated #12
Comments
@eappel HTTP header names are case insensitive, so the library currently lowercases things for consistency. Have you encountered an issue in the wild where this is a problem? |
Yeah the API I'm dealing with is case-sensitive 😞 I definitely agree that it shouldn't matter though so I'll file a ticket on the backend 👍 |
@eappel I think we should probably change this behavior on our end, too! |
@eappel We have an idea that should make it easy to fix this in the future, but we haven't quite finalized the tools yet. We'll leave the issue open for now, but will hopefully get to close it in the next month or two! |
In this example, I'm supplying an uppercased request header but it's getting lowercased somewhere within the parsing library. I couldn't easily figure out where this was happening to fix with a PR so opening as an issue!
printed:
["uppercased-header": "VALUE"]
expected:
["UPPERCASED-HEADER": "VALUE"]
The text was updated successfully, but these errors were encountered: