How to Propagate the X-Forwarded-For Header to WLS Managed Server to Get the Client IP Address for Logging
(Doc ID 1310268.1)
Last updated on SEPTEMBER 21, 2020
Applies to:Oracle WebLogic Server - Version 8.1 and later
Information in this document applies to any platform.
***Checked for relevance on 10-Mar-2016***
***Checked for relevance on 07-May-2018***
After upgrading from Oracle Application Server OC4J 10g based environments to WebLogic Server, some applications might not log the client IP address because the legacy application server was using X-Forwarded-For (XFF) to achieve the same.
Applications will be unable to get client IP addresses on WebLogic Server when the requests are routed through load balancer (BigIP) and Oracle HTTP Server (OHS).
When using Client BigIP load balancer OHS WLS, the X-Forwarded-For header was listing the load balancer IP as opposed to Client IP.
How can the client IP be propagated within the X-Forwarded-For header?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document