This content has been marked as final. Show 1 reply
I've resolved the issue from using the article from these guys:
It required a change on the WebLogic to enable the wl_proxy plug-in in the domain Configuration > Web Application: '*WebLogic Plugin Enabled* - specifies whether or not the proprietary WL-Proxy-Client-IP header should be honored. (This is needed only when WebLogic plugins are configured.)'