[ http://issues.apache.org/jira/browse/MYFACES-548?page=comments#action_12331335 ]
Carsten Fregin commented on MYFACES-548: ---------------------------------------- Oh... sorry, Martin. I had written some more text. Somehow it didn't survived the commit. If you call getRequestURI from a filter and cookies are disabled. you get the ;jsessionid part appended to your link. Normally, you would not see the ;jsessionid at all. The resource extention does not take count on it; meaning, you get an exception, that the resource could not be found. I am not sure about servlet specification. Could be a bug or a feature *g* Nevertheless, we could either check, if there is a jsessionid and remove the part before loading the resource or try to get mortbay up to clarify/fix the difference of getRequestURI called in a filter or in a jsp. I think, it is somehow a feature, because you could intercept the jsession in a filter and rewrite it on the fly. > Jetty HttpServletRequest.getRequestURI() appends the jesessionid if called in > a filter. That affects all components using the ExtentionFilter resources. > -------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: MYFACES-548 > URL: http://issues.apache.org/jira/browse/MYFACES-548 > Project: MyFaces > Type: Bug > Components: Tomahawk > Versions: 1.1.1 > Environment: Jetty 5.1.4 > Reporter: Carsten Fregin > > If you call getRequestURI inside a filter, you get it in a format like > /images/test.jpg -- 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
