Java Https clients I've seen (BEA WLS and a SOAP client and small Https
client demo programs) always produce tcp resets instead of clean tcp
closes.
This plays out in one of two ways:
1. the client ssl close notify is sent but the client closes the socket
before receipt of the peer's close notify. The client tcp will reject the
peer's close notify with a reset RST - the client socket is closed. This
is
the case for BEA WLS and the SOAP client.
2. the client tcp simply sends reset RST and doesn't even attempt an ssl
shutdown and a clean tcp close. This is the case for all of the Https
client
demo programs I've run accross.
The Java version is 1.5.
--
Posted via NewsDemon.com - Premium Uncensored Newsgroup Service
------->>>>>>http://www.NewsDemon.com<<<<<<------
Unlimited Access, Anonymous Accounts, Uncensored Broadband Access
