Mailing-List: contact modules-dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: modules-dev@httpd.apache.org
Received-SPF: pass (athena.apache.org: domain of abiacco@formatdynamics.com
 designates 209.111.94.85 as permitted sender)
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Subject: rewrite processing before cache
Date: Mon, 1 Mar 2010 18:36:37 -0700
Message-ID: 
 <40D5E3C3CBE03D45A776E7C358BDE9080199DEDA@missoula.formatdynamics.com>
Thread-Topic: rewrite processing before cache
Thread-Index: Acq5qMyv3J0B8QFqR9ymCPWZwCwZbA==
From: "Anthony J. Biacco" <abiacco@formatdynamics.com>
To: <modules-dev@httpd.apache.org>

I asked a vaguely similar question about a year ago, but this one is a
little more simplistic in comparison.

Running 2.2.14 on linux, disk caching a servlet's output, not ignoring
query string as that can change the output, and not using
cacheignoreheaders.

My problem is, using rewrite rules on such requests don't always get
triggered.
For example, if I'm trying to block a browser through a rewrite rule for
a request to said servlet, sometimes the cache takes over and serves the
cached output instead of following the rewrite. i.e. sometimes the
browser will get blocked and sometimes it will get cached content.
I'm wondering what's the workflow on such a scenario, and how can I
configure it so the rewrite always gets processed before a cache check,
if possible.

Thanx,

-Tony
---------------------------
Manager, IT Operations
Format Dynamics, Inc.
303-573-1800x27
abiacco@formatdynamics.com
http://www.formatdynamics.com