On Sun, 14 Sep 2003, Andreas Rieke wrote:

> one can only see that packets are sent since everything is encrypted, but my
> application works). As they should, neither cURL nor apache send F (fin) or
> R (reset) packets. Since apache is (by default) configured to kill
> persistent connections after 15 seconds, an F packet is sent by apache after
> that time (and curl sends an ack for that). So far, so good.
>
> However, curl seems not to recognize that the connection is gone. When a new
> request is started, cURL tries to use the old connection which it has
> acknowledged to be finished a few seconds before. As apache sends a reset
> for that immediately, cURL starts a new connection and performs the requst
> without further problems.

It would be interesting to know what curl thinks of this first connection
internally. It sounds as if the code doesn't notice the disconnect but it
wrongly believes the connection is still around when it wants to do the next
connection.

Would you be able to use a debugger to see if you can verify this in the
source?

> Has anybody seen similar things? Is there any workaround or bugfix available
> for this problem?

I've not seen this, and if you can provide an example that shows this on a
public URL it would be really cool.

-- 
 Daniel Stenberg -- curl: been grokking URLs since 1998
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf