Menu

Lumen help

Properties (V2)

Important: This guide is for the V2 version of Media portal only. If you’re using V3, please refer to Configuration Management for V3, and if you are on V1.5, please note that this version has now been deprecated and we invite you to read our guide on migrating to V3.

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.

Adding a Property to a Configuration

To add a property to a configuration, sign into Media Portal , open the Caching page by navigating to My Services > Caching, and select the access group, Service Component ID (SCID) and the configuration you want to work with, then click on “Edit Configuration”. In the “Properties” section, click on “Add Property” to open the properties menu. Here, fill in the required information.

 

  • Type the origin host name and select which protocol to use when contacting the origin from the “Cache Fill Protocol” drop-down list.

     

  • In the “Cache Fill Port” field, type which port the origin server is listening on (e.g., 80 for HTTP and 443 for HTTPS).

     

  • If you need to specify a webroot other than /, type it in the “Alternate Web root” field.

     

  • If you need to override the host header for routing purposes, type it in the “Origin DNS” field. (You can use a fully qualified domain name or an IPv4/v6 address.)

     

  • Use the checkboxes to indicate whether you'll be receiving requests via HTTP, HTTPS, or both. If you select HTTPS or both, you must:

     

    • select service type from the “Service Type” list. If you select SNI, select the radio button for the certificate you want to use for this property. You need to add your SSL certificate before you can select this option.

       

    • If you want to "staple" a certificate status to the certificate chain, select the OCSP (online certificate status protocol) checkbox.

       

    • If you want to enable HTTP/2, select the Http2 checkbox.

       

    • From the “Encryption Level” list, select the level of encryption: Risky, Default, or Advanced. (If you selected Basic as your service type and you selected the Http2 checkbox, Media Portal automatically selects Advanced.) In the Certificate section, select the radio button next to the certificate  (standard or Let's Encrypt) you want to use. (To use a Let's Encrypt certificate, you must select both HTTP and HTTPS checkboxes and your list of aliases must match the list in your certificate.)

       

  • Now, add any aliases you want the Lumen CDN to serve in addition to the host name. In the “Alias” field, type the fully qualified domain name. To add another alias, click “Add Row” and type another fully qualified domain. Repeat until you’ve added all the aliases you wish to add.

     

  • from the Traffic Type list, select the type of traffic served by the origin.

     

    • “Live” should be used for live/linear HTTP Adaptive Streaming services which can be 24x7 or events-based.

       

    • “Patch” should be used for large objects such as software updates, games etc.

       

    • “VOD” should be used for video-on-demand content served using HTTP Adaptive Streaming technologies.

       

    • “Wholesite” should be used for enterprise website delivery.

       

  • When you add a property to a configuration, you have to add at least one property-based setting (traffic type, which we have covered in the previous step). You can add additional property-based settings at the same time, but you can also add more later. Remember that the CDN applies these property-based settings to all requests to any alias defined within the property. If you don’t wish to add additional property-based settings, click “Done”, and save your configuration. The next subsection will guide you on adding property-based settings to the property.

Adding Property-based Settings to a Property

Property-based settings define the default behavior for all aliases for the property. If you need to add property-based settings to the property, select the type of property-based setting you want to add to the property from the “Add Setting” list (in the “Property-Based Settings” section) and Media Portal adds a section for that type of definition. For each definition type you selected, use the list to select a definition(s) you want to add as a property-based setting. Use the expandable sections below to learn more about how to add each type of property-based setting.

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.

From the “Add Settings” list, select “Accept-Encoding”. From the list, select the accept-encoding definition you want to apply as a property-based setting.

You can apply AWS4 authentication definitions at the property level (creating a global policy). From the “Add Settings” list, select “AWS4 Authentication”. Then, select the AWS4 authentication definition you want to add as a property-based setting.

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.

From the “Add Settings list”, select “DCT”, and then select the DCT definition you want to apply as 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.

From the “Add Settings” list, select “Log Extras” and In the field, add the Log Extras you want the CDN to send with the log.

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.

From the “Add Settings” list, select “Log Extras” and In the field, add the Log Extras you want the CDN to send with the log.

You can apply Lua scripting definitions at the property level (creating a global Lua policy). From the “Add Settings” list, select “Lua Scripting”. In the “Available Definitions” section, select the Lua-scripting definition(s) you want to add as property-based settings, then click the arrow to move the definition(s) to the Added Definitions section.

When you're finished adding the property, click “Done”. If you need to edit or add other definitions, properties, or match rules, continue editing the configuration without saving. (Saving the configuration creates a new version.) When you're done editing the configuration, click “Save” (above the “Service-Wide Definition” section). You can also click “Save As” to save the configuration under a new name. If needed, add any notes to describe the changes you made and click “Save” again. Media Portal will save the configuration.