Use uppercase first letter in HTTP header keys

[florianbehrens]

Any HTTP server I know (but, honestly, I don't know many) use uppercase first letters in HTTP header keys (e.g., 'Transfer-Encoding' rather than 'transfer-encoding').

[vinipsmaker]

From a "pure" point of view, there is nothing wrong with what I'm doing and I'd like to say "no, I won't fix that" with a load of arguments back to you.

But... you might want to obfuscate the fact that you're using Boost.Http (there are several reasons to do that). So I'm not going to reply that with "won't fix" (even if I want to).

If I only see what is relevant for this issue, the headers are present in Boost.Http at two different layers. The first layer is the user layer and I'll definitively not change that because of a silly reason like this (and this would be a change that doesn't even make sense to all HTTP backends).

The second layer is the specific implementation basic_socket, a model of the Socket concept. I could add a "policy" (or other term, if you may) template argument to this socket in which I could put an enum where the user could choose to send "all lowercase", "all uppercase" or "Camel-Case". I already plan to introduce this "policy" to specify parser options like "maximum header size" and others.

[florianbehrens]

ACK...seems to be a reasonable solution.