PQ69512: IPLANET WEBSERVER CONFIGUREDPORT 86 BUT WEBSPHERE PLUGIN CODE IS LOOKING FOR REQUESTS ON PORT 80 INSTEAD | |||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description Websphere Application Server V4.04 Solaris V5.8 iPlanet V4.1 Customer applied plugin cumulative efix from 11/12/02 and now his iPlanet webserver which is configured for port 86 won't serve requests. The plugin code fails to match virtual host. It wants to match iPlanet webserver to port 80 instead of port 86 which iPlanet is listening on. Plugin trace entries of error: TRACE: ws_common: websphereFindServerGroup: trying to match a route for: vhost='load02-pmpca.lmig.com'; uri='/PCA/PCA.do' TRACE: comparing 'load02-pmpca.lmig.com:86' to 'load02-pmpca. lmig.com:80' in VhostGroup TRACE: failed to match: load02-pmpca.lmig.com:80 no route found TRACE: failed to find a server group ... After customer removes the cumulative plugin efix, he could access his application with no problems. They are also using DNS to map their URLs (including the port numbers) to their webservers. This problem is showing up on all DNS-mapped URLs, though this was not a problem before they applied the efix. ...... Per L3, the change of the vhost matching so we use the port number the browser sent the request to is breaking some configurations. The main point of the fix was to get the correct port number for redirects up to the application server, a goal that doesn't require us to use that port for vhost matching.Local fix Problem summary **************************************************************** * USERS AFFECTED: WebSphere Application Server plugin users * * moving from 4.0.3 or lower to 4.0.4 or * * higher. * **************************************************************** * PROBLEM DESCRIPTION: Change in port number handling may * * cause configuration problems. * **************************************************************** * RECOMMENDATION: * **************************************************************** PQ62683, in addition to fixing the port numbers for redirects, changed the vhost matching so it uses the port number from the host header rather than the port number the request was received on. This causes problems with some configurations that depend on the physical port number being used rather than the host header port number. Until PQ69512, we've told customers to change their plugin-cfg to use the host header ports to work around the problem. PQ69512 provides an easier way to accomplish this by just turning on a compatability switch in the plugin-cfg rather than having to go in and change all of the port numbers.Problem conclusion This APAR provides a switch mechanism to get the old matching behavior, without affecting the PQ62683 sendRedirect() fix.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: PQ81793 Modules/Macros
SRLS
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ69512
IBM Group: Software Group
Modified date: Dec 5, 2003
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.