Inconsistency in how a request URI is determined
------------------------------------------------
Key: STS-575
URL: http://www.stripesframework.org/jira/browse/STS-575
Project: Stripes
Issue Type: Bug
Components: ActionBean Dispatching
Affects Versions: Release 1.5
Reporter: Ben Gunter
Assignee: Ben Gunter
Fix For: Release 1.5.1
AnnotatedClassActionResolver#getRequestedPath(..) returns the URI of the
request, but it does so by constructing it from getServletPath() +
getPathInfo(). All the clean URL code calls getRequestURI() instead. This can
cause tricky problems during development with some URLs that are able to
resolve the ActionBean but not to parse the URI parameters. For example, given
a prefix mapping of /action/* and @UrlBinding("/action/foo/{$event}/{param}"),
the URI //myContext/action/foo/bar/blah would correctly resolve to an
ActionBean because getServletPath() returns /action instead of //action, but
getRequestURI() returns //myContext/action/foo/bar/blah, which the URI
parameter parsing code cannot handle.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://www.stripesframework.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Stripes-development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/stripes-development
