[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [patch] IP-based virtual server support, 2.4.9-ac5-C0

Ingo Molnar <mingo@elte.hu> writes:

> based on suggestions on this list i reworked TUX's virtual server support,
> which is available in the newest TUX patch:
>   http://redhat.com/~mingo/TUX-patches/tux2-full-2.4.9-C0.bz2
>   http://redhat.com/~mingo/TUX-patches/tux2-full-2.4.9-ac5-C0.bz2

 Just a couple of typos.

> in this case the local address of the connection is used as a directory
> name in docroot. Eg. if the absolute docroot is /var/www/html/, and the IP
> address of eth0 is, the IP address of eth1 is, then all
> requests coming from eth0 will be served from the /var/www/html/
> directory, and all requests from eth1 are served from the
> /var/www/html/ directory. The actual Host: fields in the requests
 This should obviously be "/var/www/html/" for eth1.

> are ignored. An unlimited number of interfaces and IP addresses can be
> used.
> in the case of 'mixed' virtual serving:
>         echo 2 > /proc/sys/net/tux/virtual_server

 And this should be...

        echo 3 > /proc/sys/net/tux/virtual_server

> both the IP address and the Host: field (if existent) are used to
> determine the virtual docroot - eg. in the above example, if a request
> comes from eth0, and the browser sends "Host: www.site.com", then the
> virtual docroot is /var/www/html/ While i dont

James Antill -- <james@and.org>
Firewall n.
 1. A bad security program used to make other bad security programs less
baddly in need of security.

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index] []