i guess the requested URL is my problem too. let's say the user should =
www.calendar.ca to get to the calendar-server (port 81) and www.mail.ca =
get to the mail-server (port 80).

would the configuration look like this:

build squid with ./configure --disable-internal-dns

http_port 80
http_port 81

http_access allow all # to make it short and simple for this example

httpd_accel_host XXXXXXXXXXXXX # what here? the www.canada.ca
httpd_accel_port 0
httpd_accel_single_host off
httpd_accel_with_proxy on
httpd_accel_uses_host_header on

/etc/hosts # at the reverse proxy server www.mail.ca www.calendar.ca

as i sad, the requested URL is my problem. i don't know wich URL i have =
request from a client und by which criteria the reverse-proxy desides =
web-server to use.=20
does the hosts entries must also be mad on the clients, so they don't =
the general DNS-server what ip is behind www.mail.ca=20


> -----Urspr=FCngliche Nachricht-----
> Von: Henrik Nordstrom [mailto:hno@squid-cache.org]
> Gesendet: Donnerstag, 26. Februar 2004 21:50
> An: Tim Neto
> Cc: Henrik Nordstrom; martin.mueller@stadt.wolfsburg.de;
> squid-users@squid-cache.org
> Betreff: Re: AW: AW: [squid-users] reverse-proxy for multiple domains
> On Thu, 26 Feb 2004, Tim Neto wrote:
> > 1 Squid firewall machine.=A0=A0 Internet:

> Intranet:
> > =A0=A0=A0 2 Internal Web Servers.
> > =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 E-Mail server:=A0 =
> > =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 Calendar server:=A0=A0 =
> What I am missing from this is how you want the two servers=20
> to look like=20
> to the users of the reverse proxy. What URLs should the users=20
> request to=20
> end up in the respective server?
> > I can if need be re-align the Calendar server to port 80, but...

> If you want users to externally request the Calendar server=20
> as if it ran=20
> on port 80 you should re-align it to actually run on port 80.
> The use of port 81 for public web servers is not recommended.=20
> Public web=20
> servers should run on port 80 for http:// or 443 for=20

https://, nothing=20

The use of different ports in the public URL than what the actual =
runs on is also not recommended, as this often causes problems where =
internal port leaks out to the browsers, often as part of plain normal=20

> So far I have tried the virtual
> =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 httpd_accel_host virtual

this is not what you want to use, as explained earlier. You only want =
directive if you want to provide IP based accelerator setups, and the =
of this directive absolutely REQUIRES a redirector helper to fix up the =

URLs accordingly.

In all other accelerator setups httpd_accel_host SHOULD be set to your
main domain name to support prehistoric HTTP/1.0 clients not sending =

> =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 httpd_accel_port 80

ok, but you must then use a redirector to rewrite the port to 81 on=20
requests for the calendar server.

The other alternative is to use two http_port directives and virtual=20
accelerator port

http_port 80
http_port 81
httpd_accel_port 0

this will use whatever http_port the request was accepted on as port=20
number in the requested URL.

> =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 httpd_accel_single_host =

> =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 httpd_accel_with_proxy on
> =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 =

httpd_accel_uses_host_header on