Search results

Once you enable a second production slot for a SCID, you can adjust the traffic allocation for the two slots. To promote a different configuration into a slot, you need to change the configuration in that slot to 0% first.

Once you push a configuration to a production slot, Lumen adds the CName (canonical name) information for each of the aliases. You can view the CName information in Media portal.

Creating an accept-encoding definition allows you to specify extensions and compression types that should be accepted if included in a client’s request.

Use a response-header definition to return custom header responses to specific requests.

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. Remember that the CDN applies these property-based settings to all requests to any alias defined within the property.

If you no longer need a configuration, you can delete it from its service component ID (SCID). You can delete a configuration only if it isn't currently promoted to an environment.

You can view a history of the configurations promoted to the staging and production environments for a service component ID (SCID).

Dynamic content transformation (DCT) allows your origin server to serve a single variant of an object, either identity or gzip, and have the Lumen CDN dynamically transform that content into the desired variant. Use a DCT definition to specify the file extensions you want DCT applied to.

To do A/B testing with configurations in production, you can enable a second production slot for a SCID. Once you enable the second production slot, you can then change the traffic allocation for the slots.

Use log-streaming endpoint definitions to specify when, where, and how you want log streaming information posted to your endpoint. Logs are batched in a JSON-formatted payload and posted to your endpoint in near real time (<5 minutes).

You create an AWS4 authentication definition to provide your authentication information to AWS requests sent by HTTP.

Using Media portal, you can create a configuration to tell the Lumen CDN (content delivery network) what to do when it receives requests for your content. Once you have a configuration ready, you deploy it (promote it) to either your staging or production environment.

Use a geo-region definition to create a custom grouping of countries.

Use an IP-group definition to create a custom grouping of IP addresses.

You can view the history for a configuration, including all changes made for each version and any notes added when the configuration was saved.

Use request-header definitions to create a custom header in requests sent up stream to their origin.

After you add a configuration, you can make changes, as needed, to adjust how the Lumen CDN (content delivery network) processes requests for your content.

Use a token-authentication definition you will refer to in a token-authentication match rule.

Match rules provide the criteria for evaluating requests and responses and, when matched, specify one or more actions (e.g., setting cache expiration, calling geo definitions, content/header processing modes, etc.) for the system to take. Once a match rule criteria is matched, the system stops checking. In other words, the first match wins.

A saved configuration isn't active until you deploy it (promote it) to an environment—either staging or production. Once you promote it, Media portal lists the configuration under that environment; it may take several minutes to be fully propagated through the CDN network.