httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Plüm, Rüdiger, VF-Group" <ruediger.pl...@vodafone.com>
Subject RE: 2.2.19 (and probably earlier) won't let you make non-ssl vhosts on 443?
Date Thu, 26 May 2011 09:52:34 GMT
 

> -----Original Message-----
> From: Rainer Jung [mailto:rainer.jung@kippdata.de] 
> Sent: Donnerstag, 26. Mai 2011 11:43
> To: dev@httpd.apache.org
> Cc: users@httpd.apache.org
> Subject: Re: 2.2.19 (and probably earlier) won't let you make 
> non-ssl vhosts on 443?
> 
> On 26.05.2011 11:10, Issac Goldstand wrote:
> > I just upgraded a machine from 2.2.8 to 2.2.19 and suddenly Apache
> > wouldn't let me run non-SSL vhosts on port 443.  A snippet 
> like below:
> > 
> > <VirtualHost a.b.c.d:443>
> > DocumentRoot /home/foo/httpdocs
> > ServerName foo
> > <Directory "/home/foo/httpdocs/">
> > allow from all
> > Options +Indexes
> > </Directory>
> > </VirtualHost>
> > 
> > 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)
> > 
> > Was this an intentional decision made some while ago that I 
> just didn't
> > know about or is it a bug?
> > 
> > (I'd personally only expect to see that with an explicit 
> SSLEngine On
> > and no certificate/key files configured)
> 
> 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.

Regards

Rüdiger


Mime
View raw message