X-Forwarded-For not working in latest version

  • Resolved msalz

    (@msalz)


    8 years, 9 months ago

    I use the Sitelock plugin mainly due to the fact that I am using the Web Application Firewall service from Sitelock and I need to identify the actual source IP address of the client connecting to my web server in my WordPress application firewall (Wordfence). After upgrading, Wordfence could no longer see the client IP address, it only sees the IP address of incapsula (the web application firewall proxy provided by SiteLock). I needed to down grade back to SiteLock plugin 1.2. SiteLock 1.2 plugin properly provides the X-Forwarded-For information to WordPress, the latest plugin does not.

    FYI – About X-Forwarded-For:

    The X-Forwarded-For (XFF) HTTP header field is a de facto standard for identifying the originating IP address of a client connecting to a web server through an HTTP proxy or load balancer. This is an HTTP request header which was introduced by the Squid caching proxy server’s developers.

    https://www.ads-software.com/plugins/sitelock/

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Contributor Logan Kipp

    (@logankipp)

    msalz,

    I was not able to reproduce the behavior you described where the visitor’s origin IP was not being forwarded in argument X-Forwarded-For. However, I do see that you’re running WordPress 4.2.2 and an unspecified version of the plugin. I believe updating to the current plugin version 3.1.0 and WordPress 4.5.1 should resolve this behavior.

    Plugin Contributor Logan Kipp

    (@logankipp)

    This issue is believed to be resolved at this time as no other users have reported similar issues and no response has been received in over 7 months from the ticket author.

    • This reply was modified 7 years, 11 months ago by Logan Kipp.
Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘X-Forwarded-For not working in latest version’ is closed to new replies.