[WICKET-724] WicketFilter doesn't handle filter mapping parameter from FilterConfig properly

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.3.0-beta2
• Fix Version/s: 1.3.0-beta3
• Component/s: wicket
• Assignee: Jean-Baptiste Quenot
• Reporter: Martin Wehner
• Created: 06/Jul/07 13:07
• Updated: 11/Jul/07 20:53
• Resolved: 11/Jul/07 20:53

Description

If the filterMappingUrlPattern Parameter is supplied as initParameter of the filterConfig and the url-pattern is not explicitly read from web.xml by Wicket (i.e. getFilterPath(HttpServletRequest) not getFilterPath(String, InputStream) is used to initialize the filter path), Wicket cuts off two chars ("/"), not one char ("") from the end of the pattern and uses that to calculate the relative Path which determines if a Request is to be served by Wicket or not. This makes requests to the application homepage not work in such cases, as getRelativePath() will yields "/", which is not recognized by Wicket as homepage request in isWicketRequest().
Since you can't manually mount the homepage on "/" there's no workaround besides adding an additional slash to the filter pattern ("//*").