IP checking is implemented using two parameters:
You can define this setting centrally, in an Agent Config Object or locally, in a configuration file. For central agent configuration, you can designate this parameter as a multi-value setting. For local configuration, each entry should be added on a separate line. For example:
CustomIpHeader="HTTP_ORIGINAL_IP"
CustomIpHeader="HTTP_CLIENT_IP"
Note: The CustomIpHeader parameter can be used without a proxy address list being defined; however, the proxy definition list cannot be used without at least one custom IP header defined.
No maximum length is enforced for this parameter, and the value may be any string that contains a valid IP address, for example, 111.123.23.11. Do not enter server names or fully-qualified DNS host names.
You can define this setting centrally, in an Agent Config Object or locally, in a configuration file. For central agent configuration, you can designate this parameter as a multi-value setting. For local configuration, each entry should be added on a separate line. For example:
ProxyDefinition=111.12.1.1
ProxyDefinition=112.11.2.2
Note: These settings are independent of the TransientIPCheck and PersistentIPCheck parameters.
Note: For all traditional Web Agents, these parameters are in the WebAgent.conf file. For framework Agents, these values are in the LocalConfig.conf file.
Copyright © 2010 CA. All rights reserved. | Email CA about this topic |