According to Matt Sergeant:

> Is there any benefit of mod_proxy over a real proxy front end like "Oops"?

I've run squid as an alternative and did not see any serious
differences except that the caching was defeated about 10% of the
time even on images, apparently because the clients were hitting
the 'reload' button.   Apache gives you (a) the already-familiar
config file, (b) mod_rewrite to short-circuit image requests and
direct others to different backends, (c) all the other modules you
might want - ssl, jserv, custom logging, authentication, etc.
The main improvement I'd like to see would be load balancing and
failover on the client side of mod_proxy and some sort of IP takeover
mechanism on the front end side so a pair of machines would act as
hot spares for each other on the same IP address.  I know some work
has been done on this but nothing seems like a complete solution
yet.

Reply via email to