RE: Always get connection timeout
Date: Fri, 15 Aug 2008 13:20:28 -0700
The option for defining the timeout is:
How, though, does that affect the calculation for Curl_timeleft()?
Because it doesn't even look at that. The initial value for timeout_ms
= 30000, which is correct. The result I'm getting from Curl_timeleft()
is ALWAYS 3532134. So, by subtracting that value from my timeout set, I
end up with -3502134 - and it thinks I'm outta time.
I've tried setting options to forbid reuse and force a fresh connect,
but that doesn't seem to change anything. I'm beginning to wonder if I
have some problem with Curl_tvnow() or something???
[mailto:curl-library-bounces_at_cool.haxx.se] On Behalf Of Dan Fandrich
Sent: August 15, 2008 2:05 PM
Subject: Re: Always get connection timeout
On Fri, Aug 15, 2008 at 12:33:32PM -0700, Price, Robert wrote:
> Running on RH9, using source compiled from 7.18.2. Using ?easy? steps
to hit a
> servlet on a server as a ?ping? and am always getting error #28 ?
> After debugging into cURL, I?m always getting the same results from
> Curl_timeleft (specifically in ssluse.c, line 1775). Timeout is set
> seconds, but debugging only takes a few seconds and it always times
> really strange thing is that the resulting value for timeout_ms is
> same value = -3502134. That just doesn?t seem right?
Are you using the right data type (i.e. a long) in the curl_easy_setopt
call setting the timeout?
-- http://www.MoveAnnouncer.com The web change of address service Let webmasters know that your web site has movedReceived on 2008-08-15