On Tue, 7 Oct 2003, David Byron wrote:

> > No. curl always reads the response code, and getting a 404 is just as good
> > for curl as a 200 is. The HTTP status code does not tell curl about
> > errors, they are for the humans/programs that run curl.
>
> I haven't gotten the protocol analyzer out, but curl's trace doesn't include
> any response at all after the 100-Continue. That's why I figured there would
> be some kind of error.

You're right, if that is the case curl *should* report an error (error 52 to
be exact). It might indeed be a bug.

I'll need to write up a test case and see what I can do.

-- 
 Daniel Stenberg -- curl: been grokking URLs since 1998
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php