PQ70656: WAS V5 SERVLET FITERING DEFECT INCORRECT USE OF WRAPPERED RESPONSE AND REQUEST OBJECTS.

 Fixes are available

5.0.1: WebSphere Application Server Version 5.0 Fix Pack 1 (Version 5.0.1)
5.0.1: WebSphere Application Server Enterprise Edition Version 5.0 Fix Pack 1



APAR status
Closed as program error.

Error description
.
Servlet Spec requires that when forward/include is done using
custom
request or response wrappers, we are required to pass in the
same
objects to forwarded/included servlet, but we were creating our
request
object around it, so if application is expecting custom wrapper
it will
fail. This requirement in spec is not real obvious  as this is
listed in
a non-related section. Initially defect was deferred to next
major
release as this is not part of  CTS and also it  invloved design
changes
on our part. But seems like,  this is being used by number of
customers
so we decided to fix it. With the fix we will pass the wrappers
along
without creating our wrapper around it.
Local fix
No workaround available.
Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server developers      *
*                 using the servlet 2.3 filtering of requests  *
*                 and responses feature.                       *
****************************************************************
* PROBLEM DESCRIPTION: WebSphere is incorrectly wrappering     *
*                      the response and request objects for    *
*                      each dispatch to a resource.            *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Servlet Spec requires that when a forward/include is done
using custom request or response wrappers, we are required to
pass in the same objects to forwarded/included servlet, but we
were creating our request object around it, so if application
is expecting custom wrapper it will fail.
Problem conclusion
Dynacache will now pass the original wrappers without creating
a custom wrapper around it. Note: 
PQ69629 is a co-requisite
APAR for this fix to work correctly.
Temporary fix
PQ70656_eFix.jar
Comments
APAR information
APAR number PQ70656
Reported component name WAS BASE 5.0
Reported component ID 5630A3600
Reported release 00W
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2003-02-05
Closed date 2003-03-10
Last modified date 2003-03-10

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
CACHEMGT          

Publications Referenced

Fix information

Applicable component levels
R003 PSY    UP
R00A PSY    UP
R00H PSY    UP
R00I PSY    UP
R00S PSY    UP
R00W PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 00W
Software edition:
Reference #: PQ70656
IBM Group: Software Group
Modified date: Mar 10, 2003