Eric,
The opinions that I have got on this matter have been split. But Craigs point about 8.4 is good, so I will change the next releases of Jetty. I'll also ask the watchdog folks to add a test for it. I assume from section 4.4 that the URI will also have to be re-encoded so that getRequestURI continues to return an un-decoded URI. There will be a 4.1.B0 release with the change in tomorrow, which will be merged into JBoss CVS head soon after. I'll do a 4.0.5 release shortly as well. It will take a week or two for the change to be included in a stable JBoss release. cheers Eric Rizzo wrote: > Greg Wilkins wrote: > >>I think that the "path elements" refer to getContextPath, >>getServletPath and getPathInfo. I believe that getRequestURI >>should always return the URI of the original request, unless >>wrapped by a user. >> >>However!!! Craig McClanahan know a thing or two about servlets >>so I'll go do some checking again! >> >>Jetty used to change the getRequestURI result after a forward, but >>we changed it. From memory, I think that a watchdog test is checking for >>this.... but I'll check???? > > > Some more information courtesy of Craig: > > "Per Section 4.4 (servlet 2.3), the request path elements are context path, > servlet path, and path info. However, if you don't also change request > URI on a forward, you violate the following paragraph (also in 8.4): > > "It is important to note that, except for URL encoding > differences, the following equation is always true: > > requestURI = contextPath + servletPath + pathInfo" > > so there's no choice about updating requestURI as well." > > -- Greg Wilkins<[EMAIL PROTECTED]> http://www.mortbay.com Mort Bay Consulting Pty. Ltd. AU. +61(0)29977 2395 Mort Bay Consulting Limited. England UK. +44(0)7092063462 -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
