PK53315; 6.1.0.7: Java proxy server routing invalid request

Download Description

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 IBM® WebSphere® 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.