On Wed, 21 Oct 2020, MS via curl-library wrote:
I have discovered the problem only occurs when using libevent2 to drive the
multi interface. There is no issue using the easy interface directly, nor
using `multi_poll'.
... then the problem is probably in your event-based logic!
--
/
Dan, thanks for responding.
The software is written in Eiffel, with which I would guess you are
not familiar. And you would need to read through a significant
number of classes to get the overall picture.
I have discovered the problem only occurs when using libevent2 to
drive the multi
On Wed, Oct 21, 2020 at 03:50:00PM +0100, MS via curl-library wrote:
> Gisle: thank you for your response.
>
>
> Let's focus on the different behaviour with IPv4:
>
> Using libcurl in an application, without firewall
> operating, attempting to connect to bbc.co.uk,
> I obtain a hang with
>
> *
Gisle: thank you for your response.
Let's focus on the different behaviour with IPv4:
Using libcurl in an application, without firewall
operating, attempting to connect to bbc.co.uk,
I obtain a hang with
* Trying 151.101.64.81:80...
the only output written.
Using curl.exe I obtain
MS wrote:
1)
Using libcurl without a proxy, the verbose options shows "Trying ip address"
and nothing else.
If restricted to IPv4 it shows only one line. If IPv6 is permitted, I get a
first response that network
is not reachable and then a second response "Trying ..." which hangs.
Some
I have a hang that I am attempting to resolve.
1)
Using libcurl without a proxy, the verbose options shows "Trying ip
address" and nothing else.
If restricted to IPv4 it shows only one line. If IPv6 is permitted, I
get a first response that network
is not reachable and then a second
Hi Dan,
It seems ok when I use LOW_SPEED_LIMIT and LOW_SPEED_TIME.
If the speed is too slow, there will be a exception.
Thank you very much.
Br,
bazohong
2010/7/14 Dan Fandrich d...@coneharvesters.com
On Wed, Jul 14, 2010 at 03:56:19PM +0800, ±¦Öì wrote:
In the clinet, I use netstat -an and
When interface comes back, it will always use the previous address. But the
transfer does not resume more than one day.(One day is my longest test
period).
I have used the CONNECTTIMEOUT and FTP_RESPONSE_TIMEOUT option.
2010/7/14 Dan Fandrich d...@coneharvesters.com
On Wed, Jul 14, 2010 at
On Wed, Jul 14, 2010 at 02:26:55PM +0800, ±¦Öì wrote:
When interface comes back, it will always use the previous address. But the
transfer does not resume more than one day.(One day is my longest test
period).
I have used the CONNECTTIMEOUT and FTP_RESPONSE_TIMEOUT option.
I don't know
In the clinet, I use netstat -an and found the tcp connection is still
established.
2010/7/14 Dan Fandrich d...@coneharvesters.com
On Wed, Jul 14, 2010 at 02:26:55PM +0800, ±¦Öì wrote:
When interface comes back, it will always use the previous address. But
the
transfer does not resume more
On Wed, Jul 14, 2010 at 03:56:19PM +0800, ±¦Öì wrote:
In the clinet, I use netstat -an and found the tcp connection is still
established.
Which is what you'd see if the client lost the RST while the network
was down. Either of the LOW_SPEED or keepalive methods I suggested would
detect this.
Hi all,
I am using curl-7.18.2-6.fc10(libcurl.so.4.1.0) in linux
2.6.21.7-hrt1-WR2.0ap_standard #1 PREEMPT.
I invoked a get file transfer job, before it completes the download job,
there is a network interface down event, but this only last several seconds.
After the network interface being up
-Original Message-
From: curl-library-boun...@cool.haxx.se
[mailto:curl-library-boun...@cool.haxx.se] On Behalf Of Dan Fandrich
Sent: Wednesday, July 14, 2010 12:41 PM
To: curl-library@cool.haxx.se
Subject: Re: LibCurl Hang when download job disturbed by
network interface down
PM
To: curl-library@cool.haxx.se
Subject: Re: LibCurl Hang when download job disturbed by
network interface down
If the network interface comes back up with a new address,
then the existing connection will no longer be able to
continue and it will eventually time out (which could take
On Thu, 9 Apr 2009, Sandeep Kale wrote:
I have used mutex callbacks, however the issue of server going into a hang
state still persisted. Below is a code snippet where I suspect the issue is
present.
And is this now using a recent libcurl version?
//! Return curl error if any.
How exactly did you simulate this?
We have set the url and the port number to a non-existing server and
non-existing port. This generated the trace as below,
* About to connect() to 192.172.47.64 port 7878 (#0)
* Trying 3.142.47.64... * Connection refused
* couldn't connect to host
* Closing
Hi,
We are using the libcurl version as below,
-- libcurl version
curl 7.18.1 (sparc-sun-solaris2.10) libcurl/7.18.2 OpenSSL/0.9.8g zlib/1.1.3
Protocols: tftp ftp telnet dict ldap http file https ftps
Features: IPv6 Largefile NTLM SSL
On Mon, 6 Apr 2009, Sandeep Kale wrote:
We have developed a server which has libcurl at its heart. It processes all
kind of http / soap requests. This server goes into a hang state once it
receives a curl return code as CURLE_COULDNT_CONNECT, the server process
doesn't crash neither it
On Mon, Apr 06, 2009 at 07:32:53PM +0530, Sandeep Kale wrote:
We are using the libcurl version as below,
-- libcurl version
curl 7.18.1 (sparc-sun-solaris2.10) libcurl/7.18.2 OpenSSL/0.9.8g zlib/1.1.3
Can you reproduce this with the most recent
19 matches
Mail list logo
