[
http://www.stripesframework.org/jira/browse/STS-842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12840#comment-12840
]
Ken Koster commented on STS-842:
--------------------------------
There is a second unwanted behavior caused by this issue in UrlBindingFactory,
one manifested when executing a RedirectResolution with a target of "/".
Instead of a redirect to "/" ending up with the client requesting a
welcome-file (as defined in the web.xml) at the context root, the redirect
instead goes to the URL with a parameterized first URL component, with that
first parameter bound to the empty string. This leads to a 404 error.
So in the case of the ActionBean presented in the original problem description,
trying to redirect a user to "/" would result in a redirection to
//foo/bar/.html
(I'm not sure how the last component will be interpolated and whether .html
will be part of the produced URL. But which ever way it gets interpolated, the
core problem is still there.)
At resolution execution time, the corresponding binding for "/" gets looked up
in the UrlBindingFactory.pathCache. This cache is incorrectly populated with an
entry that has a key of "/" and a UrlBinding object for the URL with a
parameter in the first component.
> CLONE - UrlBindingFactory interprets parameters first in url as conflict
> ------------------------------------------------------------------------
>
> Key: STS-842
> URL: http://www.stripesframework.org/jira/browse/STS-842
> Project: Stripes
> Issue Type: Bug
> Components: ActionBean Dispatching
> Affects Versions: Release 1.5.1, Release 1.5.2
> Reporter: Kris Luhr
> Assignee: Ben Gunter
> Attachments: stripes-urlbinding-problem.zip
>
>
> I would like to have a parameter first in my urls, representing different
> sections of a site; eg: @UrlBinding("/{section}/foo/bar/{$event}.html")
> This UrlBinding results in a conflict between all ActionBeans using the
> {section} parameter. While debugging I find the
> UrlBindingFactory.getBindingPrototype(String uri) method ignoring the
> componentMatch when checking if we have a conflict, which seems to be a bug.
> At least in this case the result is not logical.
> Additionally when I use the url "/section1/foo/bar.html", the section
> parameter is set to "section1/foo/bar".
> This works and gives me the default handler if I dont have the section as a
> parameter. Perhaps these two issues are related?
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. SALE $99.99 this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122912
_______________________________________________
Stripes-development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/stripes-development
