> > First of all, what kernel are you running?  Are you running the
> stock kernel
> > with Slackware 7.0?
> sysadmin@www2:/usr$ uname -a
> Linux www2 2.2.16 #6 Wed Dec 13 15:18:16 /etc/localtime 2000 i686 unknown
>
> Nope, the kernel is stripped of all unneeded goodies, I don't have file
> systems other than ext2 compiled in, no sound, only my required inet
> drivers, etc.
>
> > If so, can you try upgrading to 2.2.19?  Previous
> > versions had some known TCP/IP bugs which could cause problems
> like you're
> > describing.
> >
> Out of curiosity, what problems that would only affect mod_ssl? I'll pull
> sources today for 2.2.19+

Well, there could be subtle TCP timing bugs affecting SSL connections due to
the handshaking or something, but it's really just a guess.  2.2.19 has
various security holes patched (including local root exploits) over 2.2.16,
so it's a good idea to upgrade nonetheless.

> > If that doesn't work, can you try adding this line?
> >
> > BrowserMatch "Mozilla" nokeepalive downgrade-1.0 force-response-1.0
> >
> I can do that right away.

I saw your other message, glad it got things chugging along a good rate.

> > What version of Netscape on the Mac are you using?  Are
> multiple versions of
> > Netscape affected?  And what version of Mac OS?
> >
> Mac OS 8.1/8.5/9.0/9.1 running Netscape 4.73/4.74/4.75[en_US] I
> believe all
> combinations were tested, but I won't swear to it.

I've been using Netscape 4.77 (OS 9.1 I think) on an iMac over here without
any problems and stock settings.  Before that I've used Netscape 4.76
without any problems as well.  I don't recall testing anything earlier,
although I've got a couple production sites running mod_ssl on Linux (RedHat
6.2 systems with 2.2.18/19) without any problems.

-Dave

______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl)                   www.modssl.org
User Support Mailing List                      [EMAIL PROTECTED]
Automated List Manager                            [EMAIL PROTECTED]

Reply via email to