Custom Log Field 1

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. - Advanced

This capability requires Rules Engine - Advanced Rules which must be purchased separately. Contact your CDN account manager to activate it.

Category: Logs

Purpose: Determines the format and the content that will be assigned to the custom log field in a raw log file and log data delivered via Real-Time Log Delivery. Use this feature to add request and response header values to your log data.

Raw Log Files Only: By default, the custom log field is called "x-ec_custom-1." However, the name of this field can be customized from the Raw Log Settings page.

The formatting that you should use to specify request and response headers is defined below.

Header Type	Format	Examples
Request Header	%{RequestHeaderReplace this term with the name of the desired request header.}iThis letter identifies that the header being specified provides information that is inbound to our CDN.	%{Accept-Encoding}i %{Referer}i %{Authorization}i
Response Header	%{ResponseHeaderReplace this term with the name of the desired response header.}oThis letter identifies that the header being specified provides information that is outbound from our CDN.	%{Age}o %{Content-Type}o %{Cookie}o

Header Type

Format

Examples

Request Header

%{RequestHeaderReplace this term with the name of the desired request header.}iThis letter identifies that the header being specified provides information that is inbound to our CDN.

%{Accept-Encoding}i

%{Referer}i

%{Authorization}i

Response Header

%{ResponseHeaderReplace this term with the name of the desired response header.}oThis letter identifies that the header being specified provides information that is outbound from our CDN.

%{Age}o

%{Content-Type}o

%{Cookie}o

Key information:

A custom log field can contain any combination of header fields and plain text.
Valid characters for this field include the following: alphanumeric (i.e., 0-9, a-z, and A-Z), dashes, colons, semi-colons, apostrophes, commas, periods, underscores, equal signs, parentheses, brackets, and spaces. The percentage symbol and curly braces are only allowed when used to specify a header field.
The spelling for each specified header field must match the desired request/response header name.
When specifying multiple headers, it is recommended to use a separator to identify each header.

For example, an abbreviation may be used to identify each header.

Sample Syntax:

AE: %{Accept-Encoding}i A: %{Authorization}i CT: %{Content-Type}o
This feature defines the value that will be set for the custom log field. If this feature is applied multiple times to the same request, then the last instance applied to the request will overwrite all previous instances.

Learn more about the custom log field (RTLD).

Learn more about the custom log field (raw log files).

Default Value: