The Lumen Caching service gives you a flexible and cost-effective solution to deliver your digital content to web users across the globe. To get started, please use the following sections to help you set up your configuration and related settings, and deploy them to production.
Configurations tell the Lumen CDN (content delivery network) what to do when it receives requests for your content. You use definitions, properties, and match rules to build a configuration. Then, you promote the configuration to an environment to activate it.
Configurations (V2) section covers the process of configuring your Caching service in detail.
Service-wide definitions are collections of common configuration data that can be referenced and that influence system behavior. Examples of definitions are a geo region or IP group. In and of itself, a definition does not influence how the system processes requests. Using definitions helps you avoid having to repeat common tasks across multiple match rules. You manage them in a single list allowing for a single change to propagate through all references.
Service-wide definitions (V2) page covers in detail the various service-wide definitions possible and how to use them.
A property is a key component in a configuration and container of all match rules. It is comprised of a primary alias, 0 or more secondary aliases, and an origin.
Properties (V2) covers how to set up a property and the various property-based settings you can use to define the default behavior for all aliases of a property.
Match rules (criteria-based settings)
Match rules are the core of the configuration. They 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. Criteria-based settings are applied only if the specified criteria (a path) is met.
Match Rules (V2) covers match rules and the various available options for directives in depth.
After you create and save a configuration, it is not activated until it is deployed (promoted) to an environment. It is also possible to enable a second deployment slot, which can be utilized for A/B testing your configurations.
Deployment (V2) covers how to promote a configuration, how to enable a second deployment slot, and other related topics in detail.
Lumen CDN allows you to ask for a forced invalidation or re-validation of your content. This feature is very useful in case you have pushed some new content to your Origin, and would like it to be available to users immediately, without waiting for the Cache Control TTL to expire.
Content Invalidation (v2) covers how to force invalidation of your cached content using Media Portal.
Before creating an HTTPS property, you’ll want to upload your certificate. Using Media Portal, you can also generate a certificate signing request (CSR) you'll use to submit to your certificate authority. Media Portal also supports the use of Let’s Encrypt Certificates.
Standard Certificates (V2) and Let's Encrypt Certificates (V2) cover how to create and use the respective type of certificates in detail.