-
Notifications
You must be signed in to change notification settings - Fork 427
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
Case sensitive header names #114
Comments
hrm good idea, I will take care about it in next version. |
+1 |
3 similar comments
+1 |
+1 |
+1 |
I ran into an issue when using More info here: slogsdon/elixir-reverse-proxy#2 |
i will handle that i the next release. for now you can do |
Still seeing this issue. |
@suprafly next major release may have it though why not using the |
@benoitc Thanks. I found a work around, I messed around with using the |
HTTP Header names are case insensitive, but Hackney returns a proplist of headers and the obvious way to extract a value
proplists:get_value
is case sensitive.I would suggest either normalizing the case of the proplist keys before returning them, or return a
hackney_headers
data structure, which would encourage users to callhackney_headers:get_value(CaseInsensitiveKey, Headers, Default).
Doing this will ensure user code doesn't break if/when an HTTP intermediary changes the case of response headers (ala Amazon ELBs, Heroku's HTTP router, etc).
The text was updated successfully, but these errors were encountered: