[
http://issues.apache.org/jira/browse/WICKET-149?page=comments#action_12456559 ]
Nathan Hamblen commented on WICKET-149:
---------------------------------------
When I was working from the trunk a few weeks ago I didn't have any trouble
with a blank filterPath; I don't have it checked out right now to check tho.
This is what the stack looks like when it's looking for "path" in a map that's
keyed by "/path":
Thread [SocketListener0-1] (Suspended (breakpoint at line 924 in
WebRequestCodingStrategy$MountsMap))
WebRequestCodingStrategy$MountsMap.strategyForPath(String) line: 924
WebRequestCodingStrategy.urlCodingStrategyForPath(String) line: 295
WebRequestCodingStrategy.targetForRequest(RequestParameters) line: 357
DefaultRequestTargetResolverStrategy.resolve(RequestCycle,
RequestParameters) line: 84
DefaultWebRequestCycleProcessor(AbstractCompoundRequestCycleProcessor).resolve(RequestCycle,
RequestParameters) line: 47
DataRequestCycle(RequestCycle).step() line: 1008
DataRequestCycle(RequestCycle).steps() line: 1100
DataRequestCycle(RequestCycle).request() line: 454
WicketFilter.doGet(HttpServletRequest, HttpServletResponse) line: 243
WicketFilter.doFilter(ServletRequest, ServletResponse, FilterChain)
line: 122
...
> mounted URLs fail if filterPath is blank
> ----------------------------------------
>
> Key: WICKET-149
> URL: http://issues.apache.org/jira/browse/WICKET-149
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.3
> Environment: jetty 5/6
> Reporter: Nathan Hamblen
>
> The path in RequestParameters needs to begin with a "/" or it will not be
> found when checking against mounted paths. The slash is prefixed in
> WicketFilter line 545 when checking isWicketRequest(), but it is not prefixed
> later when looking for the request target. Proposed fix in patch (to be
> attached) performs this operation in ServletWebRequest.getPath(); I'm not
> sure if that is the ideal spot, but I've confirmed that it fixes the problem.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
