Skip to content

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

Open

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.

Activity

  1. deanberris commented on Nov 11, 2013

    @deanberris
    Member

    Interesting. I thought the std::multimap used in the response used a case-insensitive comparator. I'll look into this and have it fixed for 0.11 -- or if you don't mind making that fix and sending in a PR, that would be most appreciated.

  2. added 2 commits that reference this issue on Nov 27, 2013
    c1b0f16
    8d827a0
  3. added 2 commits that reference this issue on Apr 14, 2015
    f4351ad
    058b7e5
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions