Question & Answer
Question
From WASv9.0.0.11 or WASv8.5.5.16, why does HTTPServletRequest.getRemoteAddr/getRemoteHost start to return WebSphere Plugin host instead of the actual client values?
Cause
not applicable
Answer
As described in the following document, you would need to configure "trustedSensitiveHeaderOrigin" to keep the previous version behavior.
In the case of WebSphere Plugin v9.0.5.1, the program still would not be able to access the actual client value due to the following WebSphere Plugin APAR.
PH17449: WAS HTTP PLUGIN FAILS TO GENERATE $WSRA $WSRH HEADERS
https://www.ibm.com/support/docview.wss?uid=swg1PH17449
https://www.ibm.com/support/docview.wss?uid=swg1PH17449
You will see that the plugin doesn't send out the headers to WAS in the plugin trace. If this is the case, you need to apply WebSphere Plugin 9.0.5.2 fixpack.
Please note that the issue reported as PH17449 is specific to 9.0.5.1 although the APAR states the fixed code will be included in 8.5.5.17 also. This is because the code change which resulted in PH17449 and the fixed code for PH17449 are both included in 8.5.5.17. So there is no need to apply the interim fix of PH17449 for 8.5.5.16.
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Component":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Was this topic helpful?
Document Information
Modified date:
15 December 2019
UID
ibm11135137