Jump to content


GEO Location - configurable options, look at X-Forwarded-For OR source IP

This topic has been archived. This means that you cannot reply to this topic.
No replies to this topic

#1 Tyler Appling

Tyler Appling
  • Members
  • 1 posts

Posted 26 September 2018 - 01:51 PM

A large majority of our traffic comes from our CDN provider. However, the GEO location is only picking up the source address of the CDN. Barracuda Web Application Firewalls allow us to configure "Header for Client IP Address".




Specify the header name appended by the Proxy server which contains the actual client IP address. The standard headers used to store the actual client IP address are:


If you give this functionality to the WAF, why can't we have it on our F600 firewalls to QOS, allow/deny, etc. traffic from the true GEO location of the client IP?