Very good suggestion.

In fact, at this point, it would be sufficient for me to understand what
are the error messages I can get in various scenarios.

There doesn't appear to be an easy way to do this. It would have been
really great to have something like a ErrorCodes.h file listing all
error messages that the error buffer can get populated with.

Now I will be relying on grepping "failf(data" in http.c to get a
complete list.

Thanks for your help.

Vinay

-----Original Message-----
From: curl-users-bounces_at_cool.haxx.se
[mailto:curl-users-bounces_at_cool.haxx.se] On Behalf Of Daniel Stenberg
Sent: Thursday, October 26, 2006 5:24 PM
To: the curl tool
Subject: RE: "Connection Aborted" vs. "Empty reply from server"

On Thu, 26 Oct 2006, Vinay Rai wrote:

> 3. I do not have evidence to be sure that the same kind of scenario is

> causing "Empty reply from server" that was causing "Connection
Aborted"
> earlier. I was taking customer's word on it. May be it's not the same
> scenario, but there is definitely some scenario where it used to come
(and
> possibly, it will come even now if we ran into same scenario). It
would be
> great if you/someone could explain the precise reason for this.

Why bother this much? Upgrade to a recent libcurl and research the
problem
based on the existing error codes, or get the source for the version
your
customer uses and dig around in that one.

-- 
  Commercial curl and libcurl Technical Support:
http://haxx.se/curl.html