We're trying to go into Prod, but 3.5.9 is no longer on the internal
site... We have our binaries in QA as well, but... Why did 3.5.9
completely disappear? It's not in the attic either.
Thanks - H
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an emai
I've seen the same issues... if you google around a bit, you'll find tons of complaints about IE5.5+ and SSL negotiations. I think SSLv2 is the only one they got right, certain cipher suites appear to be hosed in SSLv3 and TLSv1. (I saw this issue go away by only having the server support SSL
Can the person from Greenpeace who directly emailed me yesterday about
nsopenssl please resend your message. I did receive it but I simply
cannot find it in my inbox, deleted items or any other folder. Very
strange.
thanks,
/s.
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this
I should go read my own ChangeLogs :)
Yes, keepalive in the server should be disabled by setting it to 0.
It's an upcoming todo item to make nsopenssl work with the core
server's keepalive mechanism but until then this should stop you from
experiencing this problem. MSIE is fairly notorious for be
I had the same problem about one year ago. I know three solutions:
(1) disable "keepalive" (unfortunatelly it disables "keepalive" also for
connections handled by "nssock" driver);
(2) add "Connection: close" output header to every page handled
by "nsopenssl" driver (but it slows down ever
Hi there,
On Thu, 13 Nov 2003 07:28:51 -0500, Vince Ciganik <[EMAIL PROTECTED]> wrote:
>This may be similar to a problem I had a while ago. If I remember
correctly
>the symptoms; if you went to a secure page, and sat there for a while, then
>went to another page, you would get a "page not found"
This may be similar to a problem I had a while ago. If I remember correctly
the symptoms; if you went to a secure page, and sat there for a while, then
went to another page, you would get a "page not found" error. What I had to
do was to change the keepalivetimeout parameter to 0 in the nsd.tcl f
This kind of problem is notoriously difficult to reproduce and will
require an extensive code review on my part to identify where the
problem may be occurring. It is possible that I am doing/not doing
something in the code that is contributing to this. I'll see if I can
track down the problem, but
Hi there,
I reported a similar problem in April (search for Hallenberg):
http://listserv.aol.com/cgi-bin/wa?
A2=ind0304&L=aolserver&P=R2218&I=-3&X=5BD33E6DF0631E5F50&[EMAIL PROTECTED]
http://listserv.aol.com/cgi-bin/wa?
A2=ind0304&L=aolserver&D=0&I=-3&X=5BD33E6DF0631E5F50&[EMAIL PROTECTED]&P=371
