Learn F5 Technologies, Get Answers & Share Community Solutions Join DevCentral

Filter by:
  • Solution
  • Technology
code share

Akamai True-Client-IP Header Persistence

Problem this snippet solves:
For customers leveraging Akamai, all traffic is routed through Akamai regional servers. This means using source address persistence will severely limit load distribution. While cookie persistence is an ideal option, persisting via Akamai's True-Client-IP header can be a good fallback. Akamai inserts this header in each request with a value of the original user's IP address.
How to use this snippet:
This rule only requires an LTM license and should run on v9-11. Make sure to use a OneConnect profile on the virtual server to ensure
Tested on Version:
Comments on this Snippet
Comment made 30-Jan-2015 by Jason Rahm
Contributed by Chris Miller
Comment made 18-Apr-2016 by jaiAdityaSingla 240
if we enable X-forward-insert in the HTTP profile, would also do the same job instead of using the iRule here, Request Headers Received at the Server would have the actual client IP. Jason/Chris please correct me if I'm wrong?
Comment made 21-Apr-2016 by Manjunath Murugan 0
Hi .. Nice code .. Can u share me some description about this ?? I am new to persist feature . If possible , please share some O/P examples
Comment made 14-Nov-2016 by Matthew Siers 0

Cool thanks. This is good for Silverline gen knowledge since a few of our customers usually end up coming via ADN/CDN, etc.

Comment made 29-Dec-2016 by Rory Hewitt F5 107

Note that whilst the default value of the 'True Client IP' passed through from Akamai is indeed True-Client-IP, your Akamai configuration may use a different value... Check in your Akamai config first.