On Thu, 11 Jun 2009 00:24:52 +0200 (CEST) Daniel Stenberg <[email protected]> wrote:
> On Wed, 10 Jun 2009, Cosmin Luţă wrote: > > > I'm attaching a dump from "tcpdump -i lo -s 1500 -w capture.tcp > > tcp" which indicates that the server actually sends the "blax" > > string to the client. > > Right, but you send a HTTP response code 123. What exactly do you > want libcurl to do with that? It is the reason for this behavior. We > could possibly change it, but 123 is not a legitimate HTTP response > code... > Indeed, this seems to be the reason. I was testing using this code since I'm writing a protocol over HTTP and I use a couple of non-standard HTTP response codes which will be interpreted by the client. I'm going to try and use standard HTTP codes.. Thanks.
