Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: pass (herse.apache.org: local policy)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: Re: AW: [Fwd: Re: Apache 2.2.3 mod_proxy issue]
Date: Tue, 31 Oct 2006 17:10:54 +0100
Message-ID: 
 <F6E88684A95CDB4DBBD5B9F4C1C4B09B020EB5F4@vis01-mx02.vis.internal.vodafone.com>
Thread-Topic: Re: AW: [Fwd: Re: Apache 2.2.3 mod_proxy issue]
Thread-Index: Acb9BlVUAaoRZzqfRJ2lyEL2kxOfOwAADXGg
From: =?iso-8859-1?Q?Pl=FCm=2C_R=FCdiger=2C_VF_EITO?=
 <ruediger.pluem@vodafone.com>
To: <dev@httpd.apache.org>


> -----Urspr=FCngliche Nachricht-----
> Von: Jim Jagielski=20
> Gesendet: Dienstag, 31. Oktober 2006 17:05
> An: dev@httpd.apache.org
> Betreff: Re: AW: [Fwd: Re: Apache 2.2.3 mod_proxy issue]
>=20
>=20
> >=20
> > I am a regexp fan and have mod_rewrite loaded in any of our=20
> servers =3D
> > anyway
> > for some standard tasks, so this actually does not bother me :-).
>=20
> My "concern" is that the proxy-selection and operation should be
> fast, as fast a possible, and mod_rewrite simply isn't the fastest
> puppy in the world. Avoiding full-blown regex in ProxyPass allows
> for nice pattern matching (globbing) without the overhead of
> a full regex engine... fast fast fast should be the name of
> the game.

That depends on the usage of the proxy. In the example given we talk =
about
a connection to a jsp in the backend. I am pretty sure that =
mod_rewrite's
part on the total response time / resource consumption (CPU / memory) =
here
is fairly low. So honestly, this is not my concern here.

Regards

R=FCdiger