Re: Transparent proxy + siblings?

Thanks, but in regards to network layout, doesn't it look like this for
example:

+------+ +-------+ +--------+ +----------+
|Proxy |------------| Hub |------| Router |-------| Internet |
+------+ +-------+ +--------+ +----------+
                        |
                        |
                 +-------------+
                 | Firewall |
                 |(ipfwadm with|
                 | redirection |
                 | and port 80 |
                 | blocked) |
                 +-------------+
                        |
                        |
                  +-----------+
                  | Clients |
                  +-----------+

So clients make a request, they're intercepted at the firewall on say
eth0, then redirected via ipfwadm rules through eth1 to the proxy port on
the proxy? (and then the proxy goes off and speaks to a sibling or
whatever)

I don't see where any httpd_accel things should come in?

Or is the network layout above not the best way to do it? Or am I missing
something again? :)

> --- 1.1.22 and later ---
>
> httpd_accel virtual 80
> httpd_accel_uses_host_header on
>
> --- 1.1.21 and earlier ---
> httpd_accel www.yoursite.com 80
> httpd_accel_uses_host_header on
> (Drawback: Does not support old clients)
> or
> apply a small patch available from http://hem.passagen.se/hno/squid/
> somewhere in "old patches" and use 1.1.22 settings above.
> or
> use transproxyd in front of Squid.
> (Drawback: more processes)
>
> > Or alternatively, have I completely missed the point? :)
>
> No.
>
> ---
> Henrik Nordström
> Sparetime Squid Hacker
Received on Tue Aug 18 1998 - 14:06:28 MDT