Thanks John

Thats a bit worrying as I was under the impression that 2.1a was solid. I don't believe that I have any large posts but could you define what your calling a large post for me.

    Steve


On Tue, 2004-10-26 at 18:21, John Caruso wrote:
At Tuesday 09:59 AM 10/26/2004, John Caruso wrote:
At Monday 01:08 PM 10/25/2004, Steve wrote:

[-conn17-] Error: nsopenssl: EOF during SSL handshake
[-conn0-] Error: nsopenssl: nsdserver: connection closed by peer
[-conn15-] Error: nsopenssl: error during SSL handshake: Connection reset by peer

There's a bug in NsOpenSSLSend() in nsopenssl 2.1/2.1a; the retry code is seriously broken.  The bug results in intermittent failures of large POSTs.  This may or may not be the source of your problem, but it's worth a shot.

Ack, sorry, but I should also have mentioned in the prior posting that we tried nsopenssl 2.1a and had to ditch it because it was causing connection errors when servers tried to connect to themselves, as well as other intermittent errors.  So you may also want to try falling back to nsopenssl 2.1.

If you do and are interested in using the patch I mentioned, here's the 2.1 version:

------ 8< ----------------------------------------------
--- nsopenssl/ssl.c.orig        Wed Feb 13 19:32:45 2002
+++ nsopenssl/ssl.c     Tue Dec 30 17:31:33 2003
@@ -256,13 +256,11 @@


     int rc;
-    int total;
-
-    total = towrite;

     do {
        rc = SSL_write(ccPtr->ssl, buffer, towrite);
-       towrite -= rc;
+       if (rc > 0)
+           return rc;


 #if 0
------ 8< ----------------------------------------------

- John

--
AOLserver - http://www.aolserver.com/



To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.

-- AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.



Reply via email to