On Mon, Mar 29, 1999, John Hamlik wrote:
So which is better, SetEnvif or BrowserMatch per Toru Takinaka?
I prefer the canonical SetEnvIf, because BrowserMatch is historically and is
internally mapped to "SetEnvIf User-Agent" by mod_setenvif and mainly provided
for backward compatibility
On Sun, Mar 28, 1999, John Hamlik wrote:
The problem still exists on
https://en4.engelschall.com/manual/mod/mod_ssl
hmmm... I am checking further, will post more shortly.
Oh shit, my fault: MSIE actually comes in with a User-Agent of "Mozilla/4.0
(compatible; MSIE 5.0; Windows NT)", so the
it seems ok for me!
nt4/sp3, IE4 (4.72.2106.8)
ip 195.230.1.157, [29/Mar/1999:08:59:48 +0200] in your access log
--
Dimitar Stoikov. Primasoft Ltd, Internet Dept.
Take hold of OpenBSD - http://www.OpenBSD.org
__
Apache
This is what I know:
1) The patch from Ralf with the modified regex of ".*MSIE.*" works to
work around the issue. Seems like there must be a better way. hmmm. Has
anyone reported this to Microsoft? I know it probably wouldn't do much
good but it seems like they have a problem with a standard
So, those of you who've still problems with MSIE clients, should now apply the
appended patch to ssl_engine_kernel.c and add the following line to the
SSL-aware virtual host:
SetEnvIf User-Agent "^MSIE.*" ssl-unclean-shutdown
I think that this line is wrong.
IE 5.0 User-Agent is
Mozilla/4.0
On Mon, Mar 29, 1999, Toru Takinaka wrote:
So, those of you who've still problems with MSIE clients, should now apply the
appended patch to ssl_engine_kernel.c and add the following line to the
SSL-aware virtual host:
SetEnvIf User-Agent "^MSIE.*" ssl-unclean-shutdown
I think that this
On Mon, Mar 29, 1999, Dimitar Stoikov wrote:
it seems ok for me!
nt4/sp3, IE4 (4.72.2106.8)
ip 195.230.1.157, [29/Mar/1999:08:59:48 +0200] in your access log
Pu.. what a happy start for a week ;-)
You cannot image how much trouble the MSIE issue caused me...
On Sun, Mar 28, 1999, John Hamlik wrote:
1) The patch from Ralf with the modified regex of ".*MSIE.*" works to
work around the issue.
Fine, this means it now even works for MSIE clients.
That makes me finally _very_ happy! Puhh
Seems like there must be a better way. hmmm. Has
anyone
In which versions of MSIE did this occur?
I was thinking of a more specific regexp
so that not *all* M$IE users trigger the
unclean ssl shutdown behaviour...
/magnus
__
Apache Interface to OpenSSL (mod_ssl)
: Practical solution for MSIE problems!?
This is what I know:
1) The patch from Ralf with the modified regex of ".*MSIE.*" works to
work around the issue. Seems like there must be a better way. hmmm. Has
anyone reported this to Microsoft? I know it probably wouldn't do much
good but it
On Mon, Mar 29, 1999, Magnus Stenman wrote:
In which versions of MSIE did this occur?
Actually on MSIE version 3, 4 and 5. Look at the inital summary posting from
me. There the client versions are listed.
I was thinking of a more specific regexp
so that not *all* M$IE users trigger the
On Mon, Mar 29, 1999, John Imrie wrote:
Having read all the technical stuff about this problem could we run a test with
out the patch but killing keepalives for MSIE. I seem to remember problems with
MSIE and this before.
Ok, I've now changed the config on en4.engelschall.com to just
PROTECTED]'
Subject: RE: Practical solution for MSIE problems!?
MSIE 5.0 (Win 95) No problems
MSIE 4.0 (Win 95) No problems
___
John Imrie, Internet Technical Specialist
[EMAIL PROTECTED]
+44 (0)1732 520136
http://www.charitynet.org
* CAF - working
The problem still exists on
https://en4.engelschall.com/manual/mod/mod_ssl
hmmm... I am checking further, will post more shortly.
John
I've already applied the patch and the above two
directives to the
server on en4.engelschall.com, so for a quick test, those who
still had
problems
14 matches
Mail list logo
