On Sun, Apr 5, 2009 at 6:18 PM, J. Greenlees wrote:
> I tried specifying the name in the NameVirtualHost for 3 domains.
> [ one entry per domain, naturally. ] It was only by using the *.:80 in
> the NameVirtualHost directive, and only having the one NameVirtualHost
> for multiple vhosts that the
Morten K. Poulsen wrote: 'What are those httpd processes serving?'
Do you mean the pages as recorded in the web logs? The same sort of
stuff it serves all the time. We have only static content, nothing
that keeps people interacting, nothing larger than 2 MB. The IP
addresses of the connectors a
On Sun, Apr 5, 2009 at 12:18 PM, J. Greenlees wrote:
> I have found that NameVirtualHost foo.com:80 causes this error message.
> if you have NameVirtualHost *:80 the error goes away.
> Then specify the host name in the vhost container as has been done.
NVH doesn't do anything except when its argu
Eric Covener wrote:
> On Sun, Apr 5, 2009 at 10:58 AM, Developer wrote:
>
>> Hello,
>> I have config file like this:
>>
>> ...
>>
>>> Listen [fec0::40]:80
>>> NameVirtualHost myhost.com:80.
>>>
>>> ServerName myhost.com.
>>> ...
>>>
>>>
>
>
On Sun, Apr 5, 2009 at 10:58 AM, Developer wrote:
> Hello,
> I have config file like this:
>
> ...
>> Listen [fec0::40]:80
>> NameVirtualHost myhost.com:80.
>>
>> ServerName myhost.com.
>> ...
>>
httpd/apachectl/apache2ctl -S would probably show you that
Developer wrote:
Hello,
I have config file like this:
...
Listen [fec0::40]:80
NameVirtualHost myhost.com:80.
ServerName myhost.com.
...
All work fine, but I get error message like:
NameVirtualHost myhost.com has no VirtualHosts
on start. myhost.c
Hello,
I have config file like this:
...
> Listen [fec0::40]:80
> NameVirtualHost myhost.com:80.
>
> ServerName myhost.com.
> ...
>
All work fine, but I get error message like:
> NameVirtualHost myhost.com has no VirtualHosts
on start. myhost.com is nam
