Thanks guys. Looks like both "rewrite" and "set up document root for https
virtual host" can do the work.
I'll try "rewrite" first because it may not be good to expose a J2EE web
application's root directory.
Li
-Original Message-
From: Glen Mehn [mailto:[EMAIL PROTECTED]]
Sent: Monday,
Hi,
Thanks for all the feedbacks.. We did confirm that IE 6.0 has a bug
and it can't upgrade a 56-bit connection to a 128-bit one.. The Netscape
browser doesn't have the problem :-)..
Thanks
-Madhu
-Original Message-
From: Simon Ritchie [mailto:[EMAIL PROTECTED]]
Sent: Monday, Ja
you could also setup your ssl virtualhost with an different DocumentRoot, only
available by https (port 443) and leave your https pages there.
On Mon, Jan 14, 2002 at 11:52:06AM -, Simon Ritchie wrote:
> I guess that you want to refuse access to a page by HTTP, ftp etc, so that
> it can only
I hit a more fundamental problem with IE. According to me, it doesn't
support the keepalive messages that are needed to keep an SSL connection
open, so the connection dies when the keepalive timeout kicks in - by
default after one minute. This means that unless you request a new page
every minut
I'd
suggest you try this for SSLSessionCache instead:
SSLSessionCache
shm:logs/ssl_scache(512000)
It
seems to fix it for most users.
-John AireyInternet systems support officer, ITCSD,
Royal National Institute for the Blind,Bakewell Road, Peterborough PE2
6XU,Tel.: +44 (0) 17
I guess that you want to refuse access to a page by HTTP, ftp etc, so that
it can only be accessed via HTTPS. Is that correct? You can do that with
the apache rewrite mechanism. The rewrite guide shows how.
Simon
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECT