![]() ![]() Step three is useful when the remote user is behind a NAT network, as understand the code above, would provide the public address of the NAT router. Apache Module mod_log_config "%a") will still show the IP of the load balancer, but you can mine the header for the value set by your javascript. The web server's Remote IP-address value (e.g. "%^to") prior to the remote user's browser encrypting the HTTPS stream. The IP address value will survive HTTPS stream load balancing to be recorded in the web server logs because the value is inserted into the HTTP response header (e.g. Set the HTTP "Remote user" value through authentication/login (optional) Insert that value in the HTTP header or as a form-submit value returned to the web serverģ. Use JavaScript to determine the remote (client) IPĢ. In this very specific, but not uncommon, hosting case:ġ. via X-Forwarded-For) to pass along to the backend web servers to record along with the remote address. Unless your load balancer decrypts the HTTPS traffic, it cannot insert an origination (client) IP into the header (e.g. In this case, the web server's IP logging function will record the IP of the load balancer. One use case where you might want to combine the JavaScript solution offered by KM Perumal and the web server logging suggestion of Day is to address the case where you are using layer 7 load balancing of HTTPS traffic as encrypted IP traffic (not using the load balancer to offload HTTPS decryption) to one or more backend web servers. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |