On Monday, March 25, 2002, at 10:20 AM, Hans Juergen von Lengerke wrote:
We are currently using squid set up as a reverse proxy to accelerate
several heavy backends (mod_perl, etc) and to protect them from slow
client connections.
I am looking into replacing the squid with apache+mod_proxy.
On Mon, 25 Mar 2002, Hans Juergen von Lengerke wrote:
We are currently using squid set up as a reverse proxy to accelerate
several heavy backends (mod_perl, etc) and to protect them from slow
client connections.
I am looking into replacing the squid with apache+mod_proxy. Why?
Because
We are currently using squid set up as a reverse proxy to accelerate
several heavy backends (mod_perl, etc) and to protect them from slow
client connections.
I am looking into replacing the squid with apache+mod_proxy. Why?
Because ultimately I'd like to be able to cluster the frontend using
- Original Message -
From: Hans Juergen von Lengerke [EMAIL PROTECTED]
Date: Monday, March 25, 2002 4:20 pm
Subject: [OT] Replacing reverse squid with mod_proxy
Now I'm left with two choices: give up or try harder :-)
Before I decide for one of them I thought I'd ask on the lists
[Cross-posting to multiple mailing lists is dangerous (and a little
annoying) because people responding will usually not be members of all the
lists, and will therefore have to deal with bounces.]
On Mon, 25 Mar 2002, Hans Juergen von Lengerke wrote:
Now, I've tried to replace the squid with
Hi there,
On Mon, 25 Mar 2002, Hans Juergen von Lengerke wrote:
I am looking into replacing the squid with apache+mod_proxy.
I don't know if it will do what you need, but you might want to have
a look at mod_accel. If this URI is broken mail dapiatmaildotru
for the information.
