PQ53483: PROBLEMS HANDLING POSTED PARAMETERS | |||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||
APAR status Closed as program error. Error description WebSphere loosing parameters from request object in 4.01 aes There seems to be something not quite right about the way WS 4.x is handling POSTed parameters. WASENG POST parametersLocal fix Problem summary **************************************************************** * USERS AFFECTED: Any WebSphere Application Server customer * * who uses the POST HTTP access method. * **************************************************************** * PROBLEM DESCRIPTION: Request parameters are lost if the * * access method is POST and additional * * query string parameters are passed. * **************************************************************** * RECOMMENDATION: * **************************************************************** The method SRTServletRequest::setAdditionalQueryString was replacing the request's original query string with the value it was passed. The string passed to this method was the current query string with the new additional query string appended. The method would then clear the table that contained all the parsed parameters. This worked for GET but not for POST since the original query string did not contain the parameters read from the POST body. Any parameter passed via the POST body was lost.Problem conclusion Added WebSphere 3.5 code to WebSphere 4.0Temporary fix PQ53483_Test_AEsServer_AEServer.jarComments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ53483
IBM Group: Software Group
Modified date: May 16, 2002
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.