Search results

You can edit a scheduled report to change its frequency, recipients, appended message, or audience its visible to.

If you want to view the data for a scheduled CDN usage report without waiting for the report to run, you can manually trigger the report to run in Media portal.

If you no longer need Media portal to run and send a scheduled report, you can delete it.

In Media portal, you can schedule CDN usage reports to run automatically and be emailed to you.

The Lumen Caching and Download service gives you a flexible and cost-effective solution to deliver your digital content to web users across the globe. Learn how to manage configurations, service-wide definitions, properties, match rules, and certificates to control how your content is accessed.

By analyzing access logs, you can view utilization and performance of your websites, applications, content, and hardware/software resources. They can also help you analyze or debug new or errant functionality with your Lumen CDN service.

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.

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.

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.

You create a property to define the origin (and any aliases) and settings that apply to all requests to any alias defined in the property. Once you create a property, you can then add criteria-based settings (match rules) that apply when specific criteria are met.

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

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

You can create a certificate signing request (CSR) to send to your certificate authority first, and then upload your certificate or you can just upload your certificate if you completed the CSR process outside of Media portal.

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.

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.

If you need to re-upload a certificate, certificate bundle, private key, or change a private key password, you can make the necessary changes rather than adding a new certificate 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.

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.

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.