Does solving this problem with sweeping wildcard BrowserMatch
statements adversely affect the functionality of Apache and ModSSL?
What I getting at is, why don't we just BrowserMatch everything
and call it a day? What are be losing when we downgrade or
force 1.0?
Thanks,
Chris
WSO
At 12:38 PM 6/20/2001 -0400, you wrote:
>I can confirm that I had this same slow/hang problem with Macs running
>netscape 4.73 and 4.75, using several mod_ssl and apache version, running
>on Solaris. This was not a Linux-centric issue. It wasn't a priority for
>my client at the time, but I did send a BrowserMatch statement for them to
>try.
>
> -Brian
>
>
> >
>> 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
>
>--
>======================================================================
>Brian O'Neill @ home [EMAIL PROTECTED]
>At work I'm: [EMAIL PROTECTED]
>
>
>______________________________________________________________________
>Apache Interface to OpenSSL (mod_ssl) www.modssl.org
>User Support Mailing List [EMAIL PROTECTED]
>Automated List Manager [EMAIL PROTECTED]
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
