on 22/2/2000 3:20 PM, Igmar Palsenberg shot down the bitstream:
>> Whenever joe user pulls up his web browser and goes to www.mydomain.com, the
>> IPCHAINs box routes to 192.168.0.10 on the inside, whenever joe user pulls up
>> his browser and goes to www.myotherdomain.com, the IPCHAINs box routes to
>> 192.168.0.11 on the inside.
>
> Simply : No
>
> The only way that a webserver is able to know which domain it needs to
> server is with a HTTP 1.1 header. (I'm not in the mood to explain the HTTP
> 1.1 header :-)))
>
> ipchains has no knowledge of the HTTP protocol, so can't redirect on
> domain.
>
> No real solutions to this, execpt using multiple outside IP's.
Or a single web server running virtual domains. This single web server
would get all port 80 traffic forwarded to it and figure out the correct
domain from the HTTP header.
--
Ed Marczak, The New York Media Group, Inc.
[EMAIL PROTECTED]
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.