Robert,
I believe it is the RequestDispatcher that determines what resource a
request is dispatched to, so wrapping the request should not make a
difference in that respect.
However, once delivered to that resource, the wrapped path methods may
well influence what content is generated and returned - it depends on
the resource.
cheers
On 8 September 2012 06:45, Robert E Goff <goff1_at_us.ibm.com> wrote:
> What is the expected behavior when a request is wrapped within a filter by a
> HttpServletRequestWrapper that overrides the getServletPath() method? Does
> changing the returned value of this method affect the target resource?
>
> For example, if you requested a url:
> "http://server:port/contextRoot/servlet1" which had a filter associated it
> which wrapped the request and overrode the getServletPath() method to return
> "/servlet2" - should /servlet1's code be executed or /servlet2's?
>
> Likewise, if the original url didn't map to a servlet, but was a static
> resource and the wrapped request overrode the getPathInfo() method, does
> that affect the resource that is served up?
>
> Sincerely,
> Robert Goff
--
Greg Wilkins <gregw_at_intalio.com>
http://www.webtide.com
Developer advice and support from the Jetty & CometD experts.