Am 26.05.2011 11:10, schrieb Issac Goldstand:
> 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:
>
>
> DocumentRoot /home/foo/httpdocs
> ServerName foo
>
> allow from all
> Options +Indexes
>
>
>
> Su
On 26/05/2011 12:16, Reindl Harald wrote:
>
> Am 26.05.2011 11:10, schrieb Issac Goldstand:
>> 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:
>>
>>
>> DocumentRoot /home/foo/httpdocs
>> ServerName foo
>>
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:
>
>
> DocumentRoot /home/foo/httpdocs
> ServerName foo
>
> allow from all
> Options +Indexes
>
>
>
> Sudden
> -Original Message-
> From: Rainer Jung [mailto:rainer.j...@kippdata.de]
> Sent: Donnerstag, 26. Mai 2011 11:43
> To: dev@httpd.apache.org
> Cc: us...@httpd.apache.org
> Subject: Re: 2.2.19 (and probably earlier) won't let you make
> non-ssl vhosts on 443
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