Virtual host matching failure due to behavior changes in the plug-in from IBM HTTP Server 1.3.x to IBM HTTP Server 2.0.x

Technote (FAQ)
Problem
Changes in the plug-in for the IBM® HTTP Server from versions 1.3.x to 2.0.x might cause WebSphere® virtualhost matching to fail in the newer version.
Cause
By default, the v1.3.x plug-in uses the Web server name for virtual host matching if there is no host header; v2.0 uses localhost by default. The change was made to the v2.0.x plug-in because IBM HTTP Server is capable of hosting multiple virtual servers. Using the former behavior causes unexpected virtualhost matching failures.
Solution
Add *:80 in the virtualhost list in the WebSphere Application Server administrative console for the application server. This allows matching to the localhost hostname.

Alternatively, you can add a localhost:80 and route to a specific application.












Document Information

Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, Plug-in
Operating system(s): AIX, HPUX, Linux, Multi-Platform, Solaris, Windows
Software version: 3.5, 4.0, 5.0, 5.1, 6.0
Software edition: Edition Independent
Reference #: 1180411
IBM Group: Software Group
Modified date: 2004-09-27