Anybody have any suggestions ?
-Original Message-
From: Rob Archer
Sent: 14 June 2007 16:08
To: 'modssl-users@modssl.org'
Subject: SSL by Domain Name Error
Apache 2.2.4 Windows 2000 Server
Have c
Rob Archer wrote:
Anybody have any suggestions ?
Have created the key through open ssl and configured apache (using
http://raibledesigns.com/wiki/Wiki.jsp?page=ApacheSSL instructions) and
can access https via the IP address of the web server but not the
domain name. When trying
Do you have tags surrounding all
SSL directives in your configuration file? For example:
SSLPassPhraseDialog builtin
# etc.
Saikat Saha wrote:_module>
Apache was compiled as below
./configure --with-ldap --enable-mods-shared="all ssl ldap cache proxy
authn_alias mem_cache file_cache authn
Thanks for the response, I'm using the following in the httpd.conf
file:-
SSLMutex default
SSLRandomSeed startup builtin
SSLRandomSeed connect builtin
SSLSessionCache none
ErrorLog logs/ssl.log
LogLevel info
SSLEngine On
SSLCertificateFile conf/ssl/server.crt
SSLCertificateKeyFile conf/ssl/ser
What's the result when you set ServerName to your domain
name within the virtual host?:
ServerName example.com
SSLEngine On
SSLCertificateFile conf/ssl/server.crt
SSLCertificateKeyFile conf/ssl/server.key
Rob Archer wrote:
Thanks for the response, I'm using the following in the httpd.conf
fil
Unfortunately exactly the same, I've even put the domain name as the
virtual host and it behaves the same !!!
(i.e )
I was thinking that the way the web server is set up is by "web
forwarding", where the holders of our domain name forward requests onto
the ip address of our web server. This works
I am running Apache 2.0.59 with mod_ssl on Windows Server 2003 and am
noticing that dbm session caching is not working.
With the following configuration option:
SSLSessionCache dbm:logs/ssl-scache.log
The DIR/PAG files are created, but they are always size zero, and the
server never reuses sess
Sorry for late response on this one. This is what we have in httpd.conf
which is generated at compile time. This problem does not go away even
if I comment out last four lines and restart apache. Could you please
advise what else could be leading apache to think it is https rather
than http?
# S
