-
Notifications
You must be signed in to change notification settings - Fork 321
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
Prevent header renaming? #317
Comments
Can you explain why you might need this? |
You're not the first one who was asking this question, so I'm pretty concerned if this is really needed feature (we can probably allow pass header names without normalization) |
For me it turned out it wasn't needed I just thought it was when I got different errors from CURL when I changed the name of the headers. |
Ah. OK. Thanks. |
I think in general the way we process headers could use some work (and was a regression from my previous code). We always do duplicate allocations for headers, even if they already match the canonical format. I think we should check first if they match the canonical format, in which case the duplicate allocations should be skipped. Right now we always check and always allocate. |
Fixed in: #318 |
How can I prevent header renaming? I need to provide headers with an underscore and I can't find a way to achieve this.
The text was updated successfully, but these errors were encountered: