pxRequestor.pxReqRemoteHost has no value when ContextRewriteEnabled is true
We have a requirement to capture the machine host name and IP address of requestors logged on to the machine and we used pxRequestor.pxReqRemoteHost however when using in the prconfig.xml
<env name="initialization/SetBaseHTMLContext" value= https://xxxxx.xxx />
<env name="initialization/ContextRewriteEnabled" value="true" />
it disables or clears the pxRequestor.pxReqRemoteHost and pxRequestor.pxReqRemoteAddr in the pega clipboard
When removing it the values return the ip addresses. Looking for a workaround to keep the setbasehtmlcontext and contextrewriteenabled values.
This is on Pega 7.1.7 on AIX 7.1 using WebSphere 8.5
Allianz Technology
DE
@KeithB395 Hi, do you have the reverse proxy configured on WebSphere side? That might be the case why you are have ContextRewriteEnabled set to true, right? I believe in this case the client IP address get's replaced by the load balancer by default and you need to have an extra configuration to make it being passed to Pega (https://www.ibm.com/support/pages/node/6596061) . Also, out of curiosity, won't it be acceptable to have these logs of the clients' IPs on Websphere side instead of Pega?
Scotiabank
CA
@Oleg Shepelev At current a reverse proxy is not set on the Websphere side.
We have the ContextRewriteEnabled set to true such that we can force the https communication back to the site. Without the Rewrite it does not force the https.
No loadbalancer in the environments in this case but do have them setup in the higher environments ie NFT/Prod.
I did read that In tomcat, one needs to change the configuration in Tomcat's server.xml file to enable hostname lookups and the "enableLookups" attribute from a question posed a few years ago https://support.pega.com/question/sometimes-unable-get-machine-host-name-correctly-instead-getting-ip-address-place-host
Looking along the same lines as that setting given the differences in the environment.
Thanks.