100 Continue responses not handled

Issue #10 resolved
Magnus Henoch
created an issue

Some HTTP servers like to send a {{{100 Continue}}} header before sending the actual response. lhttpc doesn't like that; it ends up in {{{lhttpc_client:read_infinite_body}}}, where it signals an error, since HTTP 1.1 requests must have either a {{{Content-Length}}} or {{{Connection: close}}}.

It should actually just throw away the 100 response and read the next response header.

Comments (5)

  1. Anonymous
    • changed status to open

    Unless the user of the lib send the "Expect: 100-continue" header, which would mean that we can now start sending the post / put entity... I guess a first step is to just throw it away and document the lack of support for 100-continue from the client side and then maybe implement the proper behaviour...


  2. Log in to comment