X-Forwarded-For

the x forwarded for (xff) request header is a de facto standard header that helps identify the originating ip address of a client who is connecting to a web server through a proxy when a client connects directly to a server, the client's ip address is sent to the server (and is often written to server access logs) but if a client connection passes through any forward or reverse proxies, the server only sees the final proxy's ip address, which is often of little use so, to provide a more useful client ip address to the server, the x forwarded for request header is used http proxy can understand and parse related headers, but there is a need to add x forwarded for http header to packages that were sent by the client usually, load balancers handle this process if a load balancer adds this header to the client’s requests before it forwards to http proxy, then http proxy parses the header, and the client's real ip address can be shown in http proxy logs instead of the load balancer's ip address the following steps should be followed to benefit from this feature enter the kron pam cli as pamuser sudo vi /pam/http proxy/conf/http proxy properties http proxy client ip header=x forwarded for \ wq! sudo systemctl restart pam http if the page accessed by the client uses the unencrypted http protocol, the load balancer can add this tag to the plain text transmitted packages however, if the page accessed through the http proxy uses the encrypted https protocol, since the incoming packages will be encrypted, these packets must be decrypted on the load balancer and then re encrypted on the load balancer and sent to the http proxy after the relevant header is added this process can only be done by ssl offloading on the load balancer to avoid complex configurations, the most suitable method for transmitting the client ip address directly to the http proxy over the load balancer would be to run the load balancer in transparent mode