You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Igor Vaynberg (JIRA)" <ji...@apache.org> on 2011/09/17 20:17:08 UTC

[jira] [Resolved] (WICKET-3881) ServletWebRequest#getServletPath must handle bogus servlet path for filter on Tomcat

     [ https://issues.apache.org/jira/browse/WICKET-3881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Igor Vaynberg resolved WICKET-3881.
-----------------------------------

    Resolution: Won't Fix

i dont think the path is bogus, i think its actually correct based on the servlet spec. this is a pretty well known issue, people who map wicket on /* should not have index.html or welcome files specified.

> ServletWebRequest#getServletPath must handle bogus servlet path for filter on Tomcat
> ------------------------------------------------------------------------------------
>
>                 Key: WICKET-3881
>                 URL: https://issues.apache.org/jira/browse/WICKET-3881
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.4.17
>         Environment: Tomcat 5,6 and 7
>            Reporter: Sven Meier
>            Assignee: Sven Meier
>         Attachments: tomcatservletpath.zip, tomcatworkaround.diff
>
>
> Tomcat reports a bogus servletPath for a filter iff
> - welcome files are listed in web application of Tomcat's defaults
> - a welcome file exists (e.g. index.html)
> - a request comes in with an empty path
> Example:
> "/" results in servletPath "/index.html"
> See https://issues.apache.org/bugzilla/show_bug.cgi?id=50161 for a discussion.
> Due to the bogus servletPath redirects are failing. For a test you can run wicket-examples with SignApplication mapped to root:
> 	<filter-mapping>
> 		<filter-name>SignInApplication</filter-name>
> 		<url-pattern>/*</url-pattern>
>         <dispatcher>REQUEST</dispatcher>
>         <dispatcher>INCLUDE</dispatcher>
> 	</filter-mapping>
> The attached quickstart shows a possible workaround, see attached patch.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira