This is a discussion on mod_vhost cannot work with named hosts? within the Linux Web Servers forums, part of the Web Server and Related Forums category; I can't find it written anywhere that I can't use mod_vhost_alias /and/ named virtual hosts at the same ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
News <nooneherereally@hotmail.com> wrote in news:V7idnVOu1-GiGHffRVn-
qA@telcove.net: > I can't find it written anywhere that I can't use mod_vhost_alias /and/ > named virtual hosts at the same time. Is that true? I've tried, and it > doesn't seem to work, but I may not have it configured right, either. I've used both at the same time. What doesn't work for you? |
|
|||
|
Well, there's the question, I guess. If I wipe all my vhost conf's, the
vhost_alias takes over and works. But if I put in a single named-host conf, it stops working. What do you think I should look for? Jorey Bump wrote: > I've used both at the same time. What doesn't work for you? |
|
|||
|
News <nooneherereally@hotmail.com> wrote in news:afudnZ2dnZ14
_OXSnZ2dnRMJbN-dnZ2dRVn-0p2dnZ0@telcove.net: > Well, there's the question, I guess. If I wipe all my vhost conf's, the > vhost_alias takes over and works. But if I put in a single named-host > conf, it stops working. What do you think I should look for? It seems to require 2 IP addresses: NameVirtualHost * <VirtualHost 192.168.1.2> ServerName www.example.com </VirtualHost> <VirtualHost 192.168.1.3> VirtualDocumentRoot /var/www/vhosts/%0/site UseCanonicalName Off </VirtualHost> I can't mix them on the same IP address. This is on an apache 1.3.x server. I haven't checked apache 2.x. |
|
|||
|
On Thu, 04 Aug 2005 19:03:36 GMT, Jorey Bump <devnull@joreybump.com> wrote:
> News <nooneherereally@hotmail.com> wrote in news:afudnZ2dnZ14 > _OXSnZ2dnRMJbN-dnZ2dRVn-0p2dnZ0@telcove.net: > > > Well, there's the question, I guess. If I wipe all my vhost conf's, the > > vhost_alias takes over and works. But if I put in a single named-host > > conf, it stops working. What do you think I should look for? > > It seems to require 2 IP addresses: > > NameVirtualHost * > <VirtualHost 192.168.1.2> > ServerName www.example.com > </VirtualHost> > ?? I use entries like: <VirtualHost *> ServerName kernel.scrapping.cc ServerAlias *.kernel.scrapping.cc DocumentRoot /var/www/web/kernel ... </VirtualHost> For each virtual domain, no IP address needed, all on *:80. Grant. -- Whom computers would destroy, they must first drive mad. |
|
|||
|
G_r_a_n_t_@dodo.com.au wrote in
news:c115f1difst9n0ittrin050jnsobfqbnb0@4ax.com: > On Thu, 04 Aug 2005 19:03:36 GMT, Jorey Bump <devnull@joreybump.com> > wrote: > >> News <nooneherereally@hotmail.com> wrote in news:afudnZ2dnZ14 >> _OXSnZ2dnRMJbN-dnZ2dRVn-0p2dnZ0@telcove.net: >> >> > Well, there's the question, I guess. If I wipe all my vhost >> > conf's, the vhost_alias takes over and works. But if I put in a >> > single named-host conf, it stops working. What do you think I >> > should look for? >> >> It seems to require 2 IP addresses: >> >> NameVirtualHost * >> <VirtualHost 192.168.1.2> >> ServerName www.example.com >> </VirtualHost> >> > ?? I use entries like: > > <VirtualHost *> > ServerName kernel.scrapping.cc > ServerAlias *.kernel.scrapping.cc > DocumentRoot /var/www/web/kernel > ... > </VirtualHost> > > For each virtual domain, no IP address needed, all on *:80. You can't mix that with mass virtual hosting (using VirtualDocumentRoot) on the same IP. If you add this, it will break: <VirtualHost *> VirtualDocumentRoot /var/www/vhosts/%0/site UseCanonicalName Off </VirtualHost> I'm not sure why. I would want to specify some virtual hosts explicitly, then have mass virtual hosting handle the rest, without resorting to multiple IP addresses. |
|
|||
|
Jorey Bump wrote:
> You can't mix that with mass virtual hosting (using VirtualDocumentRoot) on > the same IP. If you add this, it will break: > > <VirtualHost *> > VirtualDocumentRoot /var/www/vhosts/%0/site > UseCanonicalName Off > </VirtualHost> > > I'm not sure why. I would want to specify some virtual hosts explicitly, > then have mass virtual hosting handle the rest, without resorting to > multiple IP addresses. Me too - that's why I'm frustrated with it. I'm trying it on 2.x, so there's one answer. So flexible, yet so not. My other real issue is why isn't this in the documentation anywhere!? |