tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [Bug 57559] Decoded Request URI used for Asynchronous dispatch
Date Tue, 10 Feb 2015 22:54:01 GMT

Mark Thomas <> changed:

           What    |Removed                     |Added
             Status|NEW                         |RESOLVED
         Resolution|---                         |WONTFIX

--- Comment #1 from Mark Thomas <> ---
The specification text you quoted skips over a few things. The main one is how
tricky it is to split an undecoded URI into contextPath, servletPath and
pathInfo. See the getContextPath() implementation in [1] for an idea of just
how messy this could get. I have no desire to see that sort of code in
something that is meant to be a convenience method.

Elsewhere in the Servlet spec (including for async) dispatches are handled in
terms of decoded paths relative to a context root. The convenience dispatch()
methods needs to be handled the same way to avoid a whole pile of unnecessary

If you need the original request URI it is available via the usual request

I'll raise this with the Servlet EG to see if the wording of this can be
changed/improved but - as far as Tomcat is concerned - this is a WONTFIX. Note
if the EG opt for the behavior you are asking for I'll re-open this issue.

I've added a test case that confirms the observed behavior.


You are receiving this mail because:
You are the assignee for the bug.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message