Closed DunyaKokoschka closed 7 months ago
Do you know if this is a behavior that we should have for HTTP/2 as well?
Do you know if this is a behavior that we should have for HTTP/2 as well?
I would say no until proven otherwise. AFAIK all HTTP/2 implementers properly handle header casing.
I've added some commits which address the comments. The name of the option is currently case_sensitive_headers
. And I added the docs for the option to the Mint.HTTP1.connect
method. I'm not sure if this is the correct place. I wasn't so sure about this comment: case_sensitive_headers
Also, locally the twitter integration test is failing for me with a 302 instead of a 200.
Changes Missing Coverage | Covered Lines | Changed/Added Lines | % | ||
---|---|---|---|---|---|
lib/mint/core/headers.ex | 18 | 19 | 94.74% | ||
<!-- | Total: | 54 | 55 | 98.18% | --> |
Totals | |
---|---|
Change from base Build ce8102b57a9bf8b4159cd0096b31d08b5d70ad09: | 0.08% |
Covered Lines: | 1268 |
Relevant Lines: | 1449 |
@whatyouhide I rebased and did some clean up. Do you think we are good to merge this?
i hear you want not lower header. i give you not lower header. but also i make default headers not lower if you pass in not lower option. alexi say this change is slow. i tell alexi if you care about slow why using elixir.
https://github.com/elixir-mint/mint/issues/256