httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefan Fritsch ...@sfritsch.de>
Subject Re: 2.2.19 (and probably earlier) won't let you make non-ssl vhosts on 443?
Date Mon, 30 May 2011 19:35:37 GMT
On Thursday 26 May 2011, Plüm, Rüdiger, VF-Group wrote:
> > > Suddenly caused the following fatal startup error to be logged:
> > > [error] Server should be SSL-aware but has no certificate
> > > configured [Hint: SSLCertificateFile] ((null):0)


> > Could it be this entry from the 2.2.12 changelog:
> >   *) Set Listen protocol to "https" if port is set to 443 and
> > 
> > no proto is
> > 
> >      specified (as documented but not implemented). PR 46066
> >      [Dan Poirier <poirier pobox.com>]


> Yes thats it:
> http://svn.apache.org/viewvc?view=revision&revision=727769
> 
> You should use
> 
> Listen a.b.c.d:443 http
> 
> instead of
> 
> Listen a.b.c.d:443
> 
> to fix this.


The error handling really sucks. For example, 

Listen 443
<VirtualHost *:443>
# nothing about ssl here
...
</VirtualHost>

gives the above message. Note the "((null):0)" at the end which should 
be config filename and line number. Adding "SSLEngine off" to the 
vhost still causes the same error, but this time with filename/line 
number.

Adding SSLCertificateFile+SSLCertificateKeyFile to the vhost, but 
ommiting "SSLEngine" changes the message to

"ops, no RSA, DSA or ECC server certificate found for 'localhost:0'?!"

Which is plain wrong, because the server does have a certificate. And 
port 0, seriously? Does anyone have some spare cycles to improve this?

Cheers,
Stefan


Mime
View raw message