NimbostratusHello,
The way it has been explained to me is that you may use the GeoIP data to do pool selections or branch selections or so forth. As stated above, embedding the data in your traffic is a EULA violation.
That said, I am fairly certain that you can "license" (sounds like it's just a waiver) the location database in order to be able to embed that data into your HTTP requests. You should contact your account team for more information and to get the data needed to expand your use of the feature.
More info from https://devcentral.f5.com/wiki/irules.whereis.ashx
F5’s traffic management products have a lot of power and flexibility and can make lots of decisions about traffic using the geolocation data on the BIG-IP. For example, a geolocation lookup can be used to route traffic requests to a different site, different server, different URL, or even substitute a different image, object, etc in the stream. The key is that the BIG-IP is making use of the data to make a decision to take some action. These are all allowed and in fact, intended usage of the geolocation data. Passing the data looked up to another system or displaying it back publicly is a violation of the basic data EULA. To summarize, all usage of the data must remain local to the system with the following two exceptions:
Location can be placed in an encrypted cookie for reference ONLY by other BIG-IP devicesLogging data can contain location info and collected into a central logging solution for analysis of F5 logs.
You should definitely read the data in the page linked above to get a better understanding of what you can and can't use it for.
Thanks. Josh
