Skip to content

Header field name check for "Transfer-Encoding" should be case insensitive #313

@Artalizian

Description

@Artalizian

I've created a client that needs to handle chunked messages, but these don't seem to be processed as chunks because the header field name is expected to be camel cased in cpp-netlib and my server sends them lower cased. I tracked the problem down to the following code in async_protocol_handler.cpp (line 290).

typename headers_range<basic_response<Tag> >::type transfer_encoding_range = headers.equal_range("Transfer-Encoding");

The HTTP/1.1 standard states that field names are case insensitive.

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions