|
Problem(Abstract) |
Changes in the plug-in for the IBM® HTTP Server from
releases of V1.3 to releases of V2.0 might cause WebSphere® Application
Server virtualhost matching to fail in the newer version. |
|
Cause |
By default, releases of the V1.3 plug-in use the Web
server name for virtual host matching if there is no host header. Releases
of the V2.0 plug-in use localhost by default. The
change was made to the V2.0 plug-in because IBM HTTP Server is capable of
hosting multiple virtual servers. Using the former behavior causes
unexpected virtualhost matching failures. |
|
Resolving the
problem |
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. |
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Application Servers |
IBM HTTP Server |
|
AIX, HPUX, Linux, Solaris, Windows |
1.3.12, 1.3.19, 1.3.26, 1.3.28, 2.0 |
|
Application Servers |
Runtimes for Java Technology |
Java SDK |
|
|
|
|
|
|
|