This is a discussion on Re: [stunnel-users] socket closed after SSL_write within the Stunnel Users forums, part of the Networking and Network Related category; --===============1339081343== Content-Type: multipart/signed; boundary="nextPart2263050.xxVgcGXQ8C"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
--===============1339081343==
Content-Type: multipart/signed; boundary="nextPart2263050.xxVgcGXQ8C"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit --nextPart2263050.xxVgcGXQ8C Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Monday 12 June 2006 12:01, Srilalitha Muralidhara wrote: > 2006.06.12 10:47:45 LOG7[19699:28]: SSL alert (write): warning: close > notify Clean SSL shutdown alert was received. > 2006.06.12 10:47:50 LOG3[19699:28]: SSL_read: Connection reset by peer > (131) =2E.. and then TCP RST! Strange. It looks like your application has set SO_LINGER option on its=20 socket, so it sends TCP RST instead of TCP FIN packet. Best regards, Mike --nextPart2263050.xxVgcGXQ8C Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQBEjaZm/NU+nXTHMtERAl2rAKDfLbpwBA3Or2rz+3lcfRekE7qFUgCfcRI C yn/Ea7f0iChE2jv+DFkuSvw= =cJ9Y -----END PGP SIGNATURE----- --nextPart2263050.xxVgcGXQ8C-- --===============1339081343== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ stunnel-users mailing list stunnel-users@mirt.net http://stunnel.mirt.net/mailman/listinfo/stunnel-users --===============1339081343==-- |