You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "Tom Schneider (JIRA)" <ji...@apache.org> on 2007/11/24 20:12:34 UTC

[jira] Resolved: (WW-2328) Server returns 404 error when the action URL has the format xxx.action;jsessionid=yyy

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

Tom Schneider resolved WW-2328.
-------------------------------

    Resolution: Fixed
      Assignee: Tom Schneider

Thanks for the patch!  I've reviewed and applied the patch.

> Server returns 404 error when the action URL has the format xxx.action;jsessionid=yyy
> -------------------------------------------------------------------------------------
>
>                 Key: WW-2328
>                 URL: https://issues.apache.org/struts/browse/WW-2328
>             Project: Struts 2
>          Issue Type: Bug
>          Components: Dispatch Filter
>    Affects Versions: 2.1.x
>         Environment: Windows XP, JDK 1.5, maven 2.0.7, Jetty 6.1.5, Struts 2.1.1-SNAPSHOT
>            Reporter: Thai Ha
>            Assignee: Tom Schneider
>            Priority: Blocker
>             Fix For: 2.1.1
>
>         Attachments: patch.txt, sample.zip
>
>
> Scenario:
> When the URL has the format of (xxx.action;jsessionid=yyy), the corresponding action mapping cannot be found by Dispatch Filter, as a result, the error 404 is returned. This error happens on Struts 2.1.1-SNAPSHOT, but not happens on Struts 2.0.x.
> Root cause:
> From the SVN history, I see the change at http://svn.apache.org/repos/asf/struts/struts2/trunk/core/src/main/java/org/apache/struts2/RequestUtils.java (revision 586739) makes the method RequestUtils.getServletPath(HttpServletRequest) returns the path parameters (like ;jsessionid=yyy) (if any) in the result. And the Dispatch Filter doesn't remove the path parameters before lookup action mapping. So if the request contains path parameters like (;jsessionid=), the action mapping will not be found, and the error 404 will be returned.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.