Show search and navigation.

 

Set Client IP Custom Header

Applies To:
HTTP LargeThis platform has been optimized to cache and deliver static content (e.g., HTML, CSS, JavaScript, ISO, multimedia, and software downloads, etc.) over HTTP or HTTPS.
HTTP SmallLegacy. If you are currently serving traffic over this platform, then you may continue to do so. However, we recommend that you serve your traffic over our more robust HTTP Large platform.
ADNThe Application Delivery Network platform has been optimized to deliver dynamic content (e.g., login credentials, account information, etc.) over HTTP or HTTPS. Typically, user-specific and database-driven content are served over this platform.
Rules EngineAllows the customization of how requests are handled by our CDN service. It may be used to override the default response provided by an origin server, CDN settings, and the default edge server behavior. - Basic
Rules EngineAllows the customization of how requests are handled by our CDN service. It may be used to override the default response provided by an origin server, CDN settings, and the default edge server behavior. - Advanced

Category: Headers

Purpose: Adds a custom request header that identifies the requesting client by IP address.

Configure this feature by performing the following steps:

  1. Determine whether a client's IP address will be logged via a custom header.

    Valid values are:

    Enabled Result

    Yes

    The requesting client's IP address will be logged in a custom request header.

    No

    Restores the default behavior. By default, the requesting client's IP address is not logged in a request header.

    Default Behavior: Disabled

  2. If this feature is enabled, define the name of the custom request header to which the requesting client's IP address will be logged.

    The Name option defines the name of the custom request header where the client's IP address will be stored.

    This feature allows a customer origin server to find out client IP addresses through a custom request header. If the request is served from cache, then the origin server will not be informed of the client's IP address. Therefore, it is recommended that this feature be used with ADN or assets that will not be cached.

    Please make sure that the specified header name does not match any of the following:

    • Standard request header names. A list of standard header names can be found in RFC 2616.

    • Reserved header names:

      • forwarded-for
      • host
      • vary
      • via
      • warning
      • x-forwarded-for
      • All header names that start with x-ec are reserved.