Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (athena.apache.org: domain of hassan.schroeder@gmail.com
 designates 209.85.132.240 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version
         :content-type:content-transfer-encoding:content-disposition
         :references;
        b=xlh+6oJRxwOMIg4xQSKGLPrFcqP6gLWJQ3b1PuPcNfMLr3aaQxc5App4rC6+bb9fJS
         h/7XqctOcTVH1V2M0pbplxHJBsR/daiRTRBEFaBA80qQy6xZxvJoeS16Etwxvggl8wyY
         yYrsSUnOPM4Jho6QW5hB7mbsTUcCCrD2JOit4=
Message-ID: <4eedb92a0808011548m53a5e26bpa2d628c06d1d579f@mail.gmail.com>
Date: Fri, 1 Aug 2008 15:48:30 -0700
From: "Hassan Schroeder" <hassan.schroeder@gmail.com>
To: "Tomcat Users List" <users@tomcat.apache.org>
Subject: Re: enabling/disabling a servlet filter conditionally
In-Reply-To: <48938E83.6050907@ice-sa.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <4893749F.3070701@ice-sa.com>
	 <4eedb92a0808011432w442321cob5056c5091bcaf95@mail.gmail.com>
	 <48938E83.6050907@ice-sa.com>

On Fri, Aug 1, 2008 at 3:30 PM, Andr=E9 Warnier <aw@ice-sa.com> wrote:

>> You could /probably/ -- untested conjecture -- break the FilterChain at
>> that point by forwarding to a URL for which Filter B wasn't applied (or
>> was applied only to a REQUEST rather than FORWARD.
>>
> On second read, can you elaborate on that one ?
> Do I understand correctly, as follows ?

> b) make filter A, in case it doesn't want filter B to run, change the
> request URL to, e.g., "something.abc",

yes, with the caveat that "change the request URL" means use  a
RequestDispatcher to forward the request.

The second approach which might be less obtrusive, means to define
your Filters so that Filter B is only applied to REQUESTs, e.g.

<filter-mapping>
  <filter-name>Filter_B</filter-name>
  <url-pattern>/*</url-pattern>
  <dispatcher>REQUEST</dispatcher>
</filter-mapping>

When Filter A sees the condition where Filter B should not be
applied, it forwards the request to the original request URL; now
Filter B is not part of the FilterChain because it's not a REQUEST.
Actually, you could probably do the same with Filter A, since you
presumably wouldn't need it to act on the request a second time.

Again, untested, but easy enough to try, and you don't need to make
any filename/URL-pattern changes as with the first approach.

HTH,
--=20
Hassan Schroeder ------------------------ hassan.schroeder@gmail.com

---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org