RE: HTTPAPI - SSL (fwd)

["Rick Hill" <rhill@xxxxxxxxxxxxxxxxxxxx>]

Sender: "Rick Hill" <rhill@xxxxxxxxxxxxxxxxxxxx>

I'm sorry you are correct the state does go from Established to Time-wait.   Each call thereafter starts up another netstat entry with a different port in the 49700 range.   Eventually they will drop out of the netstat status screen.   I must have looked at when the program was running in debug or something.   I do have one more piece of information,  I spoke with the guy at the remote site and he said everytime he puts a fresh copy of his executable out I can make a successful transaction but every try thereafter I get time out waiting for data.  Does anyone have any ideas as to why this is happening?   Not really sure this is even a problem with HTTPAPI itself.   But everytime he puts out a new executable I am able to send one transaction.   He is using .Net to provide this web service.



-----Original Message-----
From: owner-ftpapi@xxxxxxxxxxxxx [mailto:owner-ftpapi@xxxxxxxxxxxxx]On
Behalf Of Scott Klement
Sent: Tuesday, August 10, 2004 1:38 PM
To: ftpapi@xxxxxxxxxxxxx
Subject: Re: HTTPAPI - SSL (fwd)


Sender: Scott Klement <sk@xxxxxxxxxxxxxxxx>


Hi Rick,

> I have a program using HTTPAPI and SSL.  Why is that after I have done a
> post and the program has ended is it still leaving an open connection?
> If I do a netstat command I see that the connection is still established.

What state is the connection listed in by NETSTAT?  "Established"?
If so, that's very strange, it doesn't do that for me...

> I think this is what causing the program to fail the next time called.
> The only way I can get to connect after initial success is have the remote
> site reset on their side.  I can then send another transaction but then
> back to square one again with open connection.

Well, if it's really not disconnecting, that's a problem that should be
fixed in HTTPAPI.

If there's something else going on, though, you might try specifying
Connection: close using http_xproc() with HTTP_POINT_ADDL_HEADER.  That
will tell the remote server to immediately disconnect when the
conversation is complete.

I wonder if I should make that the default again?  It seems like we had
fewer problems when that was the default...
-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubsribe from the list send mail
to majordomo@xxxxxxxxxxxxx with the body: unsubscribe ftpapi mymailaddr
-----------------------------------------------------------------------
-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubsribe from the list send mail
to majordomo@xxxxxxxxxxxxx with the body: unsubscribe ftpapi mymailaddr
-----------------------------------------------------------------------