Author matrixise
Recipients brett.cannon, eric.araujo, ezio.melotti, maggyero, matrixise, mdk, ncoghlan, willingc
Date 2019-02-19.08:56:47
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1550566607.6.0.626202713189.issue36029@roundup.psfhosted.org>
In-reply-to
Content
Thank you for your contribution and your issue, it's really appreciated. I had a doubt about this point and I wanted to verify about the HTTP headers.

But in the previous version of this RFC7230: https://www.w3.org/Protocols/rfc2616/rfc2616.html

Here is the section 4.2 "Message Headers" of this previous RFC: https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2
where you have "Field names are case-insensitive".

We can see the RFC2616 was replaced by multiple RFCs (7230-7237) and in the RFC 7230, there is a section 3.2 where there is the description of the header fields.

In the section 3.2 of RFC7230:

3.2. Header Fields
"
Each header field consists of a case-insensitive field name followed
by a colon (":"), optional leading whitespace, the field value, and
optional trailing whitespace.
"

https://tools.ietf.org/html/rfc7230#section-3.2

So in this case, it's case-insensitive.

I think we can close this issue and the associated Pull Request.

Have a nice day and thank you,
History
Date User Action Args
2019-02-19 08:56:47matrixisesetrecipients: + matrixise, brett.cannon, ncoghlan, ezio.melotti, eric.araujo, willingc, mdk, maggyero
2019-02-19 08:56:47matrixisesetmessageid: <1550566607.6.0.626202713189.issue36029@roundup.psfhosted.org>
2019-02-19 08:56:47matrixiselinkissue36029 messages
2019-02-19 08:56:47matrixisecreate