Fix (APAR):  PK29303

Status:  Fix

Release:  6.0.2.9

Operating System:  AIX,HP-UX,i5/OS,Linux,Linux pSeries,Linux Red Hat - pSeries,Linux zSeries,OS/390,OS/400,Solaris,Windows

Supersedes Fixes:  

CMVC Defect:  xxxxxx

Byte size of APAR:  24581

Date: 2007-03-06

Abstract:  Portal is broken when routing through the proxy in Network Deployment version 6.0.2. A POST request is received with a Content-Length by the proxy, but the proxy forwards it chunke

Description/symptom of problem:  
PK29303 resolves the following problem:

ERROR DESCRIPTION:                                              
Proxy server fails when routing through a proxy server / ODR.   
Failure to upload files to struts application in portal.        

LOCAL FIX:                                                      

PROBLEM SUMMARY

USERS AFFECTED:
WebSphere Portal users of WebSphere
Application Server version 6.0.2.

PROBLEM DESCRIPTION:
Portal is broken when routing through
the proxy in Network Deployment
version 6.0.2. A POST request
is received with a Content-Length by
the proxy, but the proxy forwards it
chunked. The FileUpload class in
struts (as used by portal and others
of course) does a "getContentLength"
and if it returns -1, it fails the
upload.

RECOMMENDATION:
None

The request.getContentLength() method returns -1 when data is
forwarded to a servlet post method using chunked encoding,
This is consistent with the java specification. However, struts
incorrectly expects this method to return the content length,
and fails when it does not.

PROBLEM CONCLUSION:                                             
The change required by struts to overcome the problem is        
extensive and planned to be included in the version 6.1 service 
stream. As a workaround in version 6.0.2 only, to enable        
portal to function correctly, the getContentLength() method     
has been changed to look for a specific header field with       
name '$WSCL' in the request headers. If this is found the       
value of the field is returned as the content length,           
otherwise the method works as before.                           
                                                                
The fix for this APAR is currently targeted for inclusion       
in fixpacks 6.0.2.17 and 6.1.0.5.                               
Please refer to the recommended updates page for delivery       
information:                                                    
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980   
                                                                

Directions to apply fix:  NOTE: Choose the:
1) Release the fix applies to
2) The Editions that apply
3) Delete the Editions & Methods that do not apply and this Note

Fix applies to Editions:
Release 6.0
__ Application Server (Express or BASE)
__ Network Deployment (ND)
__ WebSphere Business Integration Server Foundation (WBISF)
__ Edge Components
__ Developer
__ Extended Deployment (XD)

Install Fix to:
Method:
__ Application Server Nodes
__ Deployment Manager Nodes
__ Both

NOTE:
The user must:
* Have Administrative rights in Windows, or be the Actual Root User in a UNIX environments.
* Logged in with the same authority level when unpacking a fix, fix pack or refresh pack.
* Be at V6.0.2.2 or newer of the Update Installer. This can be checked by reviewing the level of the Update Installer in file <was_root>/updateinstaller/version.txt.

The Update Installer can be downloaded from the following link:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991

For detailed instructions to Extract the Update Installer see the following Technote:
http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg21205400

1) Copy PKxxxxx.pak file directly to the maintenance directory

2) Shutdown WebSphere
Manually execute setupCmdLine.bat in Windows or . ./setupCmdLine.sh in Unix from the WebSphere instance that maintenance is being applied to.

3) Launch Update Installer

4) Enter the installation location of the WebSphere product you want to update.

5) Select the "Install maintenance package" operation.

6) Enter the file name of the maintenance package to install (PKxxxxx.pak file which was copied in the maintenance directory).

7) Install the maintenance package.

8) Restart WebSphere

Directions to remove fix:  NOTE:
* The user must have Administrative rights in Windows, or be the Actual Root User in a UNIX environments.
* FIXES MUST BE REMOVED IN THE ORDER THEY WERE APPLIED
* DO NOT REMOVE A FIX UNLESS ALL FIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED
* YOU MAY REAPPLY ANY REMOVED FIX

Example: If your system has fix1, fix2, and fix3 applied in that order and fix2 is to be removed, fix3 must be removed first, fix2 removed, and fix3 re-applied.

1) Shutdown WebSphere
Manually execute setupCmdLine.bat in Windows or . ./setupCmdLine.sh in Unix from the WebSphere instance that uninstall is being run against.

2) Start Update Installer

3) Enter the installation location of the WebSphere product you want to remove the fix.

4) Select  "Uninstall maintenance package" operation.

5) Enter the file name of the maintenance package to uninstall (PKxxxxx.pak).

6) UnInstall maintenance package.

7) Restart WebSphere

Directions to re-apply fix:  1) Shutdown WebSphere.

2) Follow the Fix instructions to apply the fix.

3) Restart WebSphere.

Additional Information: