Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
litespeed_wiki:config:show-real-ip-behind-a-proxy [2016/06/17 13:22]
Jackson Zhang
litespeed_wiki:config:show-real-ip-behind-a-proxy [2016/06/17 13:24] (current)
Jackson Zhang
Line 4: Line 4:
  
 To restore real visitor IPs simply enable the [[https://​www.litespeedtech.com/​docs/​webserver/​config/​general#​useIpInProxyHeader|Use Client IP in Header]] option to "​Trusted ip only" in the General Settings section of the Configuration page in your LiteSpeed Web Admin Console and [[https://​www.litespeedtech.com/​docs/​webserver/​config/​security#​accessControl_allow|add proxy IPs to trusted IP list]]. Please refer to [[litespeed_wiki:​config:​show-real-ip-behind-cloudflare|similar setting on cloudflare]]. To restore real visitor IPs simply enable the [[https://​www.litespeedtech.com/​docs/​webserver/​config/​general#​useIpInProxyHeader|Use Client IP in Header]] option to "​Trusted ip only" in the General Settings section of the Configuration page in your LiteSpeed Web Admin Console and [[https://​www.litespeedtech.com/​docs/​webserver/​config/​security#​accessControl_allow|add proxy IPs to trusted IP list]]. Please refer to [[litespeed_wiki:​config:​show-real-ip-behind-cloudflare|similar setting on cloudflare]].
 +
 +{{ :​litespeed_wiki:​config:​cloudflare-visitor-ip.png?​nolink&​500 |}}
  
 For example, a Citrix Netscaler device serves the original IP record. By setting it to use "​X-Forwarded-For",​ which is a standard header for that purpose, you should then see the visitors'​ original IPs.  For example, a Citrix Netscaler device serves the original IP record. By setting it to use "​X-Forwarded-For",​ which is a standard header for that purpose, you should then see the visitors'​ original IPs. 
  
 You may also see gateway ip/proxy ip with some null requests. This is normal. After one request is served, the IP will be reset to the LB IP  before a new request arrives. When a new request arrives with the "​x-Forwarded-For"​ header, it will be updated. For keep-alive connections,​ in between two requests, the LB IP will shown on the real time request list.  You may also see gateway ip/proxy ip with some null requests. This is normal. After one request is served, the IP will be reset to the LB IP  before a new request arrives. When a new request arrives with the "​x-Forwarded-For"​ header, it will be updated. For keep-alive connections,​ in between two requests, the LB IP will shown on the real time request list. 
  • Admin
  • Last modified: 2016/06/17 13:24
  • by Jackson Zhang