Hi,

> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
> Behalf Of Craig R. McClanahan
> Sent: Thursday, October 25, 2001 12:26 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Filters on error/index pages
>
>
>
>
> On Wed, 24 Oct 2001, Deacon Marcus wrote:
>
> > Date: Wed, 24 Oct 2001 16:20:11 +0200
> > From: Deacon Marcus <[EMAIL PROTECTED]>
> > Reply-To: [EMAIL PROTECTED]
> > To: [EMAIL PROTECTED]
> > Subject: Filters on error/index pages
> >
> > Hi,
> > Are Filters applied to index (default in folder) or error pages? I'm not
> > 100% positive from the documentation. Sorry if it's basic or
> obvious when
> > looking at source, but I'm recovering from caffeine overdose
> (my doc says
> > half of what I took should be enough to kill me ;/ ) and have killer
> > headaches so my iq and concentration ability are at 25% normal, and my
> > deadlines are near :(
> >
> > Thanks in advance, greetings, deacon Marcus
> >
> >
>
> The basic rule is that Filters are applied *only* on the originally
> requested URL from the client.  In practice, that means the following:
> - Request to a servlet or JSP page - yes
> - Static resources in the webapp - yes (*)
> - RequestDispatcher.include() - no
> - RequestDispatcher.forward() - no

BTW, is there any way to simulate filtered RD.i and RD.f? That should be
possible with a help of brigde servlet having access to Tomcat's
configuration data, right? Could you give me some clues where to start?

Is there any possibility for a webapp to get acces to Tomcat's classes? From
what I thought, it would be easy to do providing custom valve saving
reference to it's context in ServletContext's attribute, but maybe there's
some more direct way?

> - Error page - no

That hurts. Any possible workaround? Where are error pages (I need 404 only)
handled? Maybe that one should be changed and/or configurable in server.xml?

Is there anything I can do for now besides duplicating filtering logic
directly in my 404?

>
> (*) In a web-connected environment, you must ensure that your
>     configuration respects this requirement.  The mod_webapp
>     connector understands it already, but mod_jk must be explicitly
>     configured to forward requests for static resources that must
>     be filtered.

That's no problem since I use stand-alone mode only.

> Craig

Greetings, deacon Marcus

Reply via email to