On Wed, 3 Oct 2007, Sebastien WILLEMIJNS wrote:

>> We need exact details on what you did and what the acutal problem was...
>
> hum... i can not arrive to be sure to detect what is the difference between
> "curl: (28) Timeout was reached" and "curl: (28) Connection time-out"
>
> i suppose first is 10061 and second is 10060 winsock error but i'm not
> sure...

I don't know windows land very well so I can't really advice on tools to use,
but I thought there are such that can tell what system calls that fail or not,
and then you can analyze the network traffic to see what goes on there or not.

> otherwise i'm sure the "curl: (28) Operation timed out after 1 milliseconds
> with 2575 out of 7678" will be renamed in another number than 28 because it
> is a user request not any kind of network troubles ;)

You mean you're sure it can be renumbered?

You're oversimplificating this problem. A timeout is something that took
longer than it was allowed. There's actually nothing in the exit code or in
the description of it that says it strictly only applies to "a user request".
As I already explained, libcurl does a lot of timeout checks and for many
there are a default timeout that is merely altered by the user settable
timeout so when the timeout is reached, the code has no clue if it was default
or set by the user.

So again, I need to understand what the problem you see actually is so that I
then can check the code and see if I can see any obvious problem in there, or
if I can re-run curl myself and try to repeat it (most likely not under
Windows then, but...).

No, it can't be renumbered. At least that won't solve this problem.

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