PH04047: WAS PLUG-IN V9 FOR IHS V9 AND APACHE 2.4. FORWARD USERAGENT_IP TO SUPPORT USE OF MOD_REMOTEIP IN IHS V9 AND APACHE 2.4

8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21

APAR status

• Closed as new function.

Error description

• In Apache 2.4 and IHS V9, modules can lookup two kinds of
  client addresses -- the immediate TCP peer and the client
  address that may have been sent with X-Forwarded-For or other
  header by a trusted proxy.
  
  This is via these two elements:
  
  r->connection->client_ip (always TCP peer)
  r->useragent_ip (starts as TCP peer, mod_remoteip module may
  copy X-Forwarded-For in case of a trusted proxy)
  
  The plugin should use the latter under Apache 2.4 and IHS v9.
  Please note in APAR if this will affect value for $WSRA or
  other forwarded by PLG.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  IBM WebSphere Application Server Apache     *
  *                  24 plugin users                             *
  ****************************************************************
  * PROBLEM DESCRIPTION: The remote client IP is not set         *
  *                      correctly when using apache 24 and      *
  *                      the WebSphere web server plugin.        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The remote client IP may not be accurate when using apache 24.
  If the remote client IP is set using mod_remoteip and
  RemoteIPHeader then this fix is required.
  

Problem conclusion

• The WebSphere web server plugin was using the wrong data
  member to set to the remote IP for apache 24 web server users.
  Code has been corrected to obtain the value from the correct
  location.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.5.5.15 and 9.0.0.11.  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

  WEBSPHERE APP S

• Fixed component ID

  5724J0800

Applicable component levels

• R850 PSY

     UP

• R900 PSY

     UP