tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jan Ploski <jpl...@gmx.de>
Subject Re: Altering the request URI in a filter through HttpServletRequestWrapper
Date Thu, 23 Jan 2003 12:44:15 GMT
On Wed, Jan 22, 2003 at 10:24:26PM -0800, Craig R. McClanahan wrote:
> On Wed, 22 Jan 2003, Bill Barker wrote:
> 
> > Date: Wed, 22 Jan 2003 22:27:54 -0800
> > From: Bill Barker <wbarker@wilshire.com>
> > Reply-To: Tomcat Users List <tomcat-user@jakarta.apache.org>
> > To: tomcat-user@jakarta.apache.org
> > Subject: Re: Altering the request URI in a filter through
> >     HttpServletRequestWrapper
> >
> > I haven't looked to see why you are getting this particular error message,
> > but the basic idea shouldn't work.  Before your Filters are invoked, Tomcat
> > has already decided on which Servlet should handle the request at the end of
> > the pipeline.  Changing the requestURI and servletPath at this stage
> > shouldn't change the mapping.
> >
> 
> That's correct -- if you want your filter to change which servlet is
> actually invoked, using a RequestDispatcher.forward() is the way to go.

Okay, so it seems that the "redirecting" filter always has to be the
last one in the chain -- one cannot let the request pass through any
other filters after that. In my particular case, it is not a problem.

Thanks for your responses.

-JPL


--
To unsubscribe, e-mail:   <mailto:tomcat-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:tomcat-user-help@jakarta.apache.org>


Mime
View raw message