Page created: 4 Feb 2020 |
Page updated: 22 Jul 2020
If a PingDirectoryProxy Server is sitting behind an intermediate HTTP server, such as a load balancer, a reverse proxy, or a cache, then it will log incoming requests as originating with the intermediate HTTP server instead of the client that actually sent the request. If the actual client's IP address must be recorded to the trace log, enable X-Forwarded-* handling in both the intermediate HTTP server and PingDirectoryProxy Server. For PingDirectoryProxy Servers:
- Edit the appropriate Connection Handler object (HTTPS or HTTP), and set use-forwarded-headers to true.
- When use-forwarded-headers is set to true, the server will use the client IP address and port information in the X-Forwarded-* headers instead of the address and port of the entity that's actually sending the request, the load balancer. This client address information will show up in logs where one would normally expect it to show up, such as in the from field of the HTTP REQUEST and HTTP RESPONSE messages.
On the load balancer, configure settings to provide the X-Forwarded-* information, such as X-Forwarded-Host:. See the product documentation for the device type.