Fix (APAR):  PK53315

Status:  Fix

Release:  6.1.0.7,6.0.2.19

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

Supersedes Fixes:  

CMVC Defect:  PK53315

Byte size of APAR:  18297

Date: 2007-10-15

Abstract:  Invalid requests are incorrectly routed to the application server, which then returns a 404 Http response code.  The application server should not have to issue the 404, because th

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

ERROR DESCRIPTION:                                              
It is a violation of the spec for /echofoobar/echo.htm to match 
to an application with a deployed web context root of /echo. The
Java proxy server routs this request back to the application    
servers resulting in SRVE0017W instead of running the servlet.  

LOCAL FIX:                                                      
none                                                            

PROBLEM SUMMARY

USERS AFFECTED:
All users of WebSphere Network Deployment
using a proxy server.

PROBLEM DESCRIPTION:
Invalid requests are incorrectly routed
to the application server, which then
returns a 404 Http response code.  The
application server should not have to
issue the 404, because the request
should not be routed to the application
server.

RECOMMENDATION:
None

An application has a deployed web context of /echo, with a rule
to match URI's of *.htm. An invalid request of /echo123/echo.htm
is routed to the application server. It is a violation of the
spec to match the URI with a different context root to the
application. The effect of this incorrect match is that the
application server ends up returning a 404 http response code.
This error is caused because the code was not handling the lack
of a preceding slash in the uri. /*.htm would work, but *.htm
did not.


PROBLEM CONCLUSION:                                             
The code was fixed to properly handle a wildcard URI pattern    
which does not have a preceding slash, and the fix was made     
available for the 6.0.2.19 and 6.1.0.7 releases. The fix will   
be included in Service Pack 6.0.2.25 and 6.1.0.15 for WebSphere 
Application Server Network Deployment.                          


Directions to apply fix:  Fix applies to Editions:
Release 6.0
_x_ Network Deployment (ND)

Install Fix to:
Method:
__ Application Server Nodes
__ Deployment Manager Nodes
_x_ 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 6.1.0.7-WS-WASND-IFPK53315.pak (or 6.0.2.19-WS-WASND-IFPK53315.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 (6.1.0.7-WS-WASND-IFPK53315.pak (or 6.0.2.19-WS-WASND-IFPK53315.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 (6.1.0.7-WS-WASND-IFPK53315.pak or 6.0.2.19-WS-WASND-IFPK53315.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: