Forum Discussion
Presumably you've applied a SNAT, and using the XFF header as a way to get the client's true address to the web server. Short of disabling SNAT (and configuring the environment in such a way that SNAT isn't necessary), you must find some place to put this information that an application can read. A routed mode configuration would probably be the simplest, if that's one of the only ways your CMS app can see the address, but there are still other options - all highly dependent on what the CMS app is capable of:
-
The TCP::options command set allows you to read/write information into option 28 of the TCP packet.
-
You could potentially tack on query string values or embed the values in request or response content.
Can you elaborate on how the CMS app interacts?