Page cannot be displayed

Hi, We are working with apache-1.3.23 and mod_ssl-2.8.7, sometimes explorer says: "This page contains both secure and nonsecure items. Do you want to display the nonsecure items?" While everything on the page is secure, when answering yes, we always get a 'page cannot be displayed' The proble

why do I get this so often?

Does anyone know why I get this so often in my log: [Thu Aug 22 13:17:59 2002] [error] mod_ssl: SSL handshake interrupted by system [Hint: Stop button pressed in browser?!] (System error follows) [Thu Aug 22 13:17:59 2002] [error] System: Connection reset by peer (errno: 104) Almost every reques

error 104

I have this error a lot of times in my log. [Tue Aug 20 14:43:41 2002] [error] mod_ssl: SSL handshake interrupted by system [Hint: Stop button pressed in browser?!] (System error follows) [Tue Aug 20 14:43:41 2002] [error] System: Connection reset by peer (errno: 104) What does it mean? I use a

Re: Problem starting Apache (yes I have read the FAQs!)

On Tue, 20 Aug 2002 20:48:26 +0100 "Peter Viertel" <[EMAIL PROTECTED]> wrote: > there's more info on this in the reference manual, than the FAQ. > > http://www.modssl.org/docs/2.8/ssl_reference.html#ToC4 > > Basically try changing the 'startup' one to use a > file:/path/to/file/with/junk/in/it

still no message for old browsers

Hi, thanks for the tips on how to create a situation where browsers which cannot handle 128 bits encryption are redirected to an upgrade message. I get the idea of using the rewrite rules, but I'm still stuck. I have a separate directory /var/www/messages configured with rewriteEngine off, al

redirecting users part 2

Hi, I'm trying to redirect users who don't have enough encryption capabilities for 128 bit (see previous mail). I've tried the following (but it doesn't work): Add upgrade.html (the text users with old browsers are supposed to get) to index: DirectoryIndex index.html index.htm Index.html Ind

Directing users wihtou enough encryption capability

Hi, I'm trying to do the following: I have a site with strong encryption, demanding 128 bit encryption with: SSLRequire %{SSL_CIPHER_USEKEYSIZE} >= 128 A lot of users don't have browsers with 128 bits encryption capabilities, so wat I would to do is: When a user cannot use 128 bits enc