Re: Name based virtual host forwarding from Tux to Apache

[Mike Zimmerman <mike@4host.com>]

A problem with Apache and Tux is that the information needed for Apache to 
properly determine which vhost to send things to is not there.

Apache needs to use the IP of the incoming connection to determine which 
host to go to. Since the request is always on 127.0.0.1, no go.

I ended up using the below rewrite rule to do the dirty work for me.

RewriteCond ${lowercase:%{HTTP_HOST}} ^(www\.)?(.*)$
RewriteRule ^/(.*) /var/www/html/%2/$1 [L]

In this case, we need to rely completely on the Host: directive from the 
browser to decide where to go. I don't like it, but I didn't have a choice.

If someone has a better solution, I'll all eyes.

Mike

At 03:23 PM 3/4/2002 -0700, you wrote:
> OK, I have virtual hosting set up with Tux. Works great. I also have it
> set up with Apache. Also works great. When I request a php script and
> tux tries to hand it off to apache, it appears to not forward it in a
> way which allows Apache to use the correct virtual domain. I know this
> because I have set the default DocumentRoot to an invalid path. Whenever
> I ask for the script though Tux, the Apache error_log shows that bad
> DocumentRoot. When I go through Apache directly, the script executes.
> Any possible problem anyone can think of?
>
> -Eric ;-)
>
>
>
> _______________________________________________
>
> tux-list@redhat.com
> https://listman.redhat.com/mailman/listinfo/tux-list