PQ71994: WHEN JSP INCLUDES ANOTHER JSP, THE RESULT FROM WAS4.0.X IS DIFFERENT FROM WAS5.0 | |||||||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description When a jsp includes another jsp, the result in WebSphere V.4.0.x is different from the result in WebSphere V.5.0. The following is the code customer has sent in for the testing. Call 1 : <jsp:include page="/bouton.jsp" flush="true"> <jsp:param name="call" value="call1"/> <jsp:param name="submitType" value="button.login"/> </jsp:include> <BR> call 2 : <jsp:include page="/bouton.jsp" flush="true"> <jsp:param name="call" value="call2"/> <jsp:param name="resetType" value="button.reset"/> </jsp:include> ---------------- . BOUTON.JSP (the page that is included) <% String submit = null; submit = request.getParameter("submitType"); String reset = null; reset = request.getParameter("resetType"); String call = null; call = request.getParameter("call"); %> Call type = <%= call %><BR> submit = <%= submit %><BR> reset = <%= reset %><BR> --------------- . The page displayed in WebSphere V.5.0. is: Call 1 : Call type = call1 submit = button.login reset = null call 2 : Call type = call2 submit = button.login reset = button.reset . ---------------- In WebSphere V.4.0.x resulting page is: Call 1 : Call type = call1 submit = button.login reset = null call 2 : Call type = call2 submit = null reset = button.reset ------------- The result from WebSphere V.4.0.x is the one that the customer has been using. In WebSphere V.5.0, the result is different and causing problem in customer's application.Local fix Problem summary **************************************************************** * USERS AFFECTED: WebSphere Application Server users of * * Servlets and JSPs. * **************************************************************** * PROBLEM DESCRIPTION: WebSphere allows access to included * * request parameters to resources * * prior to the include being executed. * **************************************************************** * RECOMMENDATION: * **************************************************************** WebSphere incorrectly handles request parameters after a resource is dispatched to another resource via a RequestDispatcher.include() method call. Query string parameters passed to the included resource were not properly removed after the dispatch completed for the included resource. This allowed the top level resource's request object to be able to request query string data that should only have been available to the included resource.Problem conclusion Modified the handling of request parameters to properly reset state when completing a RequestDispatcher.include() method call.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
Publications Referenced
|
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 00W
Software edition:
Reference #: PQ71994
IBM Group: Software Group
Modified date: Mar 14, 2003
(C) Copyright IBM Corporation 2000, 2008. All Rights Reserved.