> Connection #0 to host 192.168.1.22 left intact
> * Connection #0 seems to be dead!
> * Closing connection #0
> * About to connect() to 192.168.1.22 port 8080 (#0)

> Am posting a HttpRequest and it says connection left intact, But after
some
> secs am posting a query its saying connection seems to be dead. Closing
> connection.
>
> Why is it so? What should I do now

libcurl does its check and considers the connection dead.

Fire up wireshark or similar and snoop the traffic to see if libcurl is
right
or not. This code works for a large number of people, platforms and networks
so I honestly think this does the right thing and that what you see is due
to
your network setup or similar.

I agree that libcurl does this check,
But am setting the option Forbid reuse to zero,
then am posting a new request on the same CURL without freeing,
Is it anything to do with the server ?

On Mon, Apr 14, 2008 at 7:03 PM, Vijay <nags.vijay_at_gmail.com> wrote:

> Hi,
>
> Connection #0 to host 192.168.1.22 left intact
> * Connection #0 seems to be dead!
> * Closing connection #0
> * About to connect() to 192.168.1.22 port 8080 (#0)
> * Trying 192.168.1.22... * Bind to local port 33300 failed, trying next
> * Local port: 33301
> * connected
> * Connected to 192.168.1.22 (192.168.1.22) port 8080 (#0)
>
> Am posting a HttpRequest and it says connection left intact,
> But after some secs am posting a query its saying connection seems to be
> dead.
> Closing connection.
>
> Why is it so? What should I do now
>
>
> --
> VIJAY

-- 
VIJAY