> >
> > >>>>> the response code is "100 continue"...
> >
> > Organox::Protocol::LibCurl::build_response: HTTP/1.1 100 Continue
> > Organox::Protocol::LibCurl::build_response: Date: Wed, 27 Mar 2002
> > 13:58:56 GMT
> > Organox::Protocol::LibCurl::__ANON__: Date: Wed, 27 Mar
> 2002 13:58:56
> > GMT
> > Organox::Protocol::LibCurl::__ANON__: Server: Microsoft-IIS/4.0
> > Organox::Protocol::LibCurl::request: final 0.002665
> > LWP::Protocol::collect: read 26458 bytes
> >
> > Anybody wonder why libcurl is closing the connection even after
> > receiving a "continue" response code?
>
> Yes, I wonder why.
>
> AFAICR, the 100-response code just eats that and then awaits
> the next "real" header so it should close the connection
> because of this.

Don't know if this is helpful at all, but I was playing with some java
libraries
Of my own maing the other day and had a similar problem. What happened
Was hat the IIS page was failing, and Microsoft in its infinite wisdom
Decided not to return a header with the error message.

So the chain of events was:
        100 - response

        text-only packet
        
        close socket.

And since he java was looking for another header it just failed to
console.

Don't know if this helps, but thought I would throw it out there.

Sam
Received on 2002-03-27