DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUGĀ·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=38390>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED ANDĀ·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=38390

           Summary: Pluto portlet fails if you set a render parameter
                    including a ; in the value
           Product: Tomcat 5
           Version: 5.5.9
          Platform: Other
        OS/Version: Linux
            Status: NEW
          Severity: major
          Priority: P2
         Component: Catalina
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: [EMAIL PROTECTED]


Problem observed in a Pluto portlet.  If you submit a form, and one of the form
fields (text box) has a ; in the value entered by the user, and you get a that
name and value from the action request (e.g. servlet request) and call
ActionResponse.setRenderRequest(name, value), then Tomcat corrupts the next
request.  This does not happen when the same code runs on Jetty.  Somehow that ;
appears to be making it into a request URL.  Following are some comments from
David DeWolf of Pluto.

-------------------------

Render parameters are stored within the url so that they persist across render
requests and do not rely on session state. The PortalControlParameter class is
primarily responsible for converting render parameters, modes, window states,
etc . . .to a portal url.

See:

http://svn.apache.org/repos/asf/portals/pluto/branches/pluto-1.0.2/portal/src/java/org/apache/pluto/portalImpl/core/PortalControlParameter.java

Also See:
http://svn.apache.org/repos/asf/portals/pluto/branches/pluto-1.0.2/portal/src/java/org/apache/pluto/portalImpl/core/PortalUrl.java

I'm trying to think of any reasons why this conversion would be dependent upon
the underlying servlet container. The only thing I can think of is that the two
containers are returning different values from request.getPathInfo() (which is
subsequently parsed back into modes, window states, and render parameters).

I would be willing to bet that the issue is with the semi-colon in the
parameter. A quick glance at the source code indicates that pluto does not treat
it as a "special" character and thus it is not encoded within the url. If that
is happening, I'll bet that tomcat is truncating pathInfo at the semi colon and
jetty is not.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to