PK55330: The port set in the host header of a request is not returned correctly.

Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR10 Cumulative Fix for WebSphere Application Server
6.1.0.31: Java SDK 1.5 SR11 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.33: Java SDK 1.5 SR12 FP1 Cumulative Fix for WebSphere
6.1.0.29: Java SDK 1.5 SR11 Cumulative Fix for WebSphere Application Server
6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server

APAR status

• Closed as program error.

Error description

• Added HTTPL URL prefix for a web service application from DM
  console. Expected, SOAP address location attribute of the WSDL
  for the particular web service will have HTTP custom prefix
  appended but it did not.  WSDL was served from WebSphere
  Process Server cluster v6.0.2.1.
  Above issue causes testing tool to fail, unable to run any
  regression test.
  

Local fix

• Our initial analysis shows , the reason for the testing tool
  failed could be because of the WSDL served from app server
  has soap address location attribute as URL domain name + app
  server port instead of only URL domain name. Since all the app
  servers are load balanced through BIG IP load balancer, we
  expected WSDL to have SOAP attribute location as only BIG IP
  domain name without any port appended. By default location
  had domain name + app server port, we tried to remove port info
  by specifying HTTP end point custom prefix from DM console that
  did not work.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: IBM WebSphere Application Server version     *
  *                 6.0.2 and 6.1 users.                         *
  ****************************************************************
  * PROBLEM DESCRIPTION: When IBM HTTP Server is replaced by a   *
  *                      different proxy server WebSphere        *
  *                      Application Server appends its port     *
  *                      number, instead of the host header      *
  *                      port, to the returned URL.              *
  *                      For example,                            *
  *                                                              *
  *                      Request:                                *
  *                        GET http;//appServer:9082/example     *
  *                        HOST:ProxyServer:8888                 *
  *                                                              *
  *                      Returned URL:                           *
  *                        http;//ProxyServer:9082               *
  *                                                              *
  *                      This problem does not exist when IBM    *
  *                      HTTP Server is in use.                  *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The method getServerPort() relies on the channel's
  getVirtualPort() which returns a port number in the following
  order:
     1. Port number from the request URL
     2. Port number from the request host header
  

Problem conclusion

• The Webcontainer was modified to return a port number from
  the host header, if any, or the URL port where the client
  connection was accepted on.  In addition to the current
  custom property "trusthostheaderport", the new custom property,
  
  "com.ibm.ws.webcontainer.extractHostHeaderPort" (default is
  false), also needs to be set for this to work properly.
  
      trusthostheaderport = true
      com.ibm.ws.webcontainer.extractHostHeaderPort = true
  
  These custom properties are not case sensitive and applicable
  to versions 6.0.2 and 6.1
  Please refer to the following technote for instructions on
  enabling WebContainer custom properties:
  http://www.ibm.com/support/docview.wss?rss=180&uid=swg21284395
  
  The fix for this APAR is currently targeted for inclusion in
  fixpacks 6.0.2.27 and 6.1.0.15
  Please refer to the recommended updates page for delivery
  information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels

• R60A PSY

     UP

• R60H PSY

     UP

• R60I PSY

     UP

• R60P PSY

     UP

• R60S PSY

     UP

• R60W PSY

     UP

• R60Z PSY

     UP

• R61A PSY

     UP

• R61H PSY

     UP

• R61I PSY

     UP

• R61P PSY

     UP

• R61S PSY

     UP

• R61W PSY

     UP

• R61Z PSY

     UP