DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10347>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10347 Path Info incorrectly processed for JSP's [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |INVALID ------- Additional Comments From [EMAIL PROTECTED] 2002-06-29 17:02 ------- For the record, Section 11.1 bullet three says ("***" added for emphasis): If the ***last*** segment in the URL path contains an extension ... which seems awfully hard to misinterpret from my perspective. Extension mapping only looks at the segment after the last '/' character. An implication of this (by the definition of extra path info) is that there never will be any. If you want the servlet spec group to look at this issue, please send feedback to the address on the spec: [EMAIL PROTECTED] and this is timely because the Servlet 2.4 spec is currently in public review, so is it's still possible to change things. One particular requirement of addressing this differently (besides the backwards compatibility impacts) is the need to establish specific rules for how to interpret potentially ambiguous URLs like: http://localhost:8080/myapp/foo.jsp/bar.jsp/baz.jsp so that all containers did them consistently. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
