Eric,
What you need to do is to add the IP address and 'secure' hostname to one
line in your hosts file, then add the below to you httpd.conf. I assume you
don't mean all hosts('secure' and 'www') from 1 IP. You will need a DNS
entry for secure.hostname.org.
VirtualHost
I am curious. IF the server certificate had a common name www.xxx.org and
the virtual host is yyy.xxx.org, should the browser considering the server
a fake?
On Tue, 11 May 1999, Derek Smith wrote:
Eric,
What you need to do is to add the IP address and 'secure' hostname to one
line in
- Original Message -
From: Lin [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, May 12, 1999 2:45 AM
Subject: Re: forcing secure via name (off topic?)
I am curious. IF the server certificate had a common name www.xxx.org and
the virtual host is yyy.xxx.org, should
I am curious. IF the server certificate had a common name www.xxx.org and
the virtual host is yyy.xxx.org, should the browser considering the server
a fake?
If the Browser talks to yyy.x:443 he expects a X509 Cert with CN=yyy.xxx
In the case described by you the CN is invalid (from browsers
Server Version: Apache/1.3.6 (Unix) mod_perl/1.19 PHP/3.0.7 mod_ssl/2.2.8
OpenSSL/0.9.2b
works fine as http and as https.
How can I force ssl when a user uses the url http://secure.hostname.org
(redirect/rewrite to https://secure.hostname.org) and deny ssl for
http(s)://www.hostname.org
I'd
Redirect / http://www.hostname.org/
/VirtualHost
Where 123.123.123.123 is your IP address. I just made all that up, so it may
or may not work :)
Cheers,
Simon Garner
- Original Message -
From: Eric Gus [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, May 11, 1999 2:21 PM
Subject
