You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
mikedilger opened this issue
Aug 27, 2015
· 2 comments
Labels
A-headersArea: headers.C-bugCategory: bug. Something is wrong. This is bad!E-easyEffort: easy. A task that would be a great starting point for a new contributor.
That's what the use of UniCase is for. However, I think the issue is in the parsing of the Connection header, in this case. Instead of being parsed as the KeepAlive variant, it's the ConnectionHeader variant.
Instead, it should do a couple comparisons instead of a match.
if s == KEEP_ALIVE{// ...}elseif s == CLOSE{// ...}
With the constants being UniCase("keep-alive") and UniCase("close").
seanmonstar
changed the title
header case insensitivity
Connection Header case insensitivity
Aug 27, 2015
seanmonstar
added
C-bug
Category: bug. Something is wrong. This is bad!
A-headers
Area: headers.
E-easy
Effort: easy. A task that would be a great starting point for a new contributor.
labels
Aug 27, 2015
A-headersArea: headers.C-bugCategory: bug. Something is wrong. This is bad!E-easyEffort: easy. A task that would be a great starting point for a new contributor.
http://tools.ietf.org/html/rfc7230#section-6.1:
I noticed that Apache Bench sends "Keep-Alive" and hyper misinterprets it
I think this may also apply to most other headers
The text was updated successfully, but these errors were encountered: