One more comment on the "defunct vhost" setup.
You have to be very careful if you decide to define each of your virtual
hosts in their own distinct definition file, and include them all with a
wildcard Include directive, such as "Include vhost.*"
I think that the order that the files are included
On Fri, Jan 13, 2012 at 4:13 PM, Clay Porter wrote:
> Thanks for the info. I will try what you suggested.
>
> I'm pretty new to all of this, so I hope you don't mind a n00b
> question. What do you mean by a "defunct vhost"? Could I trouble you
> for an example?
>
> Thanks again.
>
> Clay
>
He
Thanks for the info. I will try what you suggested.
I'm pretty new to all of this, so I hope you don't mind a n00b
question. What do you mean by a "defunct vhost"? Could I trouble you
for an example?
Thanks again.
Clay
On Thu, Jan 12, 2012 at 4:46 PM, Steve Swift wrote:
> It all looks corre
It all looks correct to me. Can you exchange the order of the VirtualHost
definitions? The first Virtualhost defined is the one that gets used if
anything goes wrong with allocating a request to a particular vhost, so you
often end up thinking you are using the first Vhost when in fact you are
usi
All,
I have two virtual hosts set up that look like the following (I've
tried to only include the information pertaining to the problem, i,e,
I've removed the actual rewrite rules, etc):
Listen *:38215
NameVirtualHost *:38215
DocumentRoot /www/sitea
ServerName www.sitea.com
ErrorLog
