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.
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.
You can view Lua-scripting definitions CDN Support has added to a configuration (at your request).
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.
If you no longer need a Let's Encrypt certificate, you can delete it from Media portal.
You can view a history of the configurations promoted to the staging and production environments for a service component ID (SCID).
If you want to manually revoke a compromised Let's Encrypt certificate, you can reissue it in Media portal.
After you create a standard or Let's Encrypt certificate, you can view details for a certificate—including pending changes—in Media portal.
You can view the history for a configuration, including all changes made for each version and any notes added when the configuration was saved.
In Media portal, you can regenerate a Let's Encrypt certificate to make changes to the certificate such as adding additional host names, updating the key encryption, or changing the common name.
You can view the status of your certificates Media portal to see which certificates are ready to use and which need your attention—maybe requiring edits.
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.