PQ65742: URI MATCHING IS INCONSISTENT BETWEEN DIFFERENT STAGES OF PLUGIN PROCESSING. ONE STAGE WILL MATCH, THE OTHER WILL NOT.

 A fix is available

4.0.5: WebSphere Application Server Version 4.0 Fix Pack 5 (Version 4.0.5)



APAR status
Closed as program error.

Error description
Has behavior changed for 4.0.4 plug-in? Because customer said th
at he sees some behavior is changed. Per customer email stated t
hat plug-in is not wokring correctly after installing PTF4.
They should show that the WAS plug-in is sending the request to
WAS when is should not. It appears to find a match on a URIGroup
s but not the virtual host so it fails, then it continues to che
ck URI Groups (so far so good) but then even though it does not
find a match for the next URI Group it checks its virtual hosts
and finds a match - this is wrong.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server users of IIS    *
*                 or IHS/apache.                               *
****************************************************************
* PROBLEM DESCRIPTION: WAS plugin matches URI in early stage,  *
*                      fails to match same URI at later stage. *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The WAS plugins were matching a URI in an early "see if
WAS should handle this request" stage, and then failing to
match the same URI once it got to the "handle the request"
stage.  The plugins would only do the false matching on
a URI that matched a UriGroup and ANY other VhostGroup.
( normally, matches are only done across the UriGroup and
VhostGroup pairs specified by the Route tags in the
plugin-cfg ).   This can only cause problems with IIS and
possibly with IHS/Apache - and even then, the majority of
customers will not have a configuration that will cause
the defect to manifest.
Problem conclusion
Fixed the glitch in the matching code that allowed this
cross-route matching to occur.
Temporary fix Comments
APAR information
APAR number PQ65742
Reported component name WEBSPHERE AE NT
Reported component ID 5630A2201
Reported release 400
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2002-08-29
Closed date 2002-09-16
Last modified date 2002-09-16

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
PLUGIN          

SRLS

Fix information
Fixed component name WEBSPHERE AE NT
Fixed component ID 5630A2201

Applicable component levels
R400 PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ65742
IBM Group: Software Group
Modified date: Sep 16, 2002