When you add a property to a configuration, you have to add at least one property-based setting (traffic type). You can add additional property-based settings at the same time, but you can add more later using the instructions below. You can add only one property-based setting for each of the types in the list. Remember that the CDN applies these property-based settings to all requests to hosts within the Origin ID.
To add a property-based setting to a property:
Dynamic content transformation (DCT) allows your origin server to serve a single variant of an object, either identity or gzip, and have the CenturyLink CDN dynamically transform that content into the desired variant.
By default, encodings are normalized to either Identity or Gzip. Any other encodings are automatically dropped from the request. However, you may override this by creating an accept-encoding definition that is attached to a property-based setting.
If you have enabled Log Streaming, the Log Extras setting allows you to automatically add static and dynamic data to the log streaming record. Dynamic content can be any number of internal variables. For example, header lines sent to a client have the prefix “sent_http_”, so to capture a custom header’s value in the client request (e.g., cdn_session), you would use $sent_http_cdn_session. If you are unsure of how to format dynamic Log Extra values, please contact CDN Support.
Any Log Extras you create must be notified to CDN Support before they will begin appearing in the log stream.
Use log-endpoint definitions to specify when, where, and how you want log information posted to your endpoint. Logs are batched in a JSON-formatted payload and posted to your endpoint in near real time (<5 minutes).