Menu

Lumen help

Adding a match rule to a configuration

  1. From the main menu, select My Services > Caching
My Service - Caching
  1. From the lists, select the access group and SCID (service component ID) you want to work with. 
My Services - Caching (with SCID selected)
  1. From the list, select the configuration. 
  1. From an open configuration, click Edit Configuration.
my services caching edit configuration
  1. From the Properties list, select the property you want to add a match rule to.

    Media portal displays the information for the property.
my services caching add configuration property selected add match rule
  1. Click Add Match Rule.
my services caching add configuration property selected add match rule.
  1. In the Match Rule Criteria field, type the path you want the CDN to look for when evaluating incoming requests.

Note: At this time, the only supported expression is the requested path/received URI without query strings.  Note that the path may be expressed using the following operators:
 

  • ==  Equality test
  • %= Equality test (case insensitive)
  • *=   Glob test
  • %*  Glob test (case insensitive)
     

Any operator may be inverted by prepending an “!” (not).

  1. If you want the CDN to look for matches exactly the way you typed the path, select the Case Sensitive check box.
  1. From the Add Setting list, choose the type of directive you want to use if an incoming request matches the path you typed. Use the sections below to learn more about how to add each type of directive.

  1. From the Add Settings list, select Cache Control.

    By default, Media portal adds internal cache control—which tells the CDN how it should cache the object.
my services caching add configuration property selected add match rule add setting cache control
  1. Select the internal policy: TTLAs-isNo-cache, or No-store. (If you select TTL, type a number and select a unit for the time to live. )
  1. If you need to set an external policy, click the External checkbox and then select the policy.

Use a deny-policy directive to reject or redirect (to an alternate URL) all requests matching specific criteria.

  1. From the Add Settings list, select Deny Policy.
my services caching-add configuration property selected add match rule add setting deny policy.
  1. Fill in the header name and value.
  1. To add additional headers, click Add Header and repeat step 2.
  1. Select the type of denial: Error Message or Redirect. If you select Redirect, type the URL where you want to send requests.

Use a geo-blocking directive to allow or deny access based on a requesting client's geographic region. You can also whitelist certain IP addresses within the region(s) to allow their access, but deny all others within the region.
  1. From the Add Settings list, select Geo Blocking.
my-services caching add configuration property selected add match rule add setting geo blocking
  1. In the Available Definitions section, select one or more definitions you want to apply to this directive.
  1. Click the right arrow to move the definition(s) to the Added Definitions section. (To remove a definition from the directive, select it in the Added Definitions section and click the left arrow).
  1. Select the radio button for action you want the CDN to take when the match is made: Allow or Deny.
  1. If you selected Deny, select whether you want to display an error or to redirect the request. If you select Redirect, type the destination in the Redirect URL field.
  1. If you need to whitelist IP addresses, select one or more IP-group definitions you want to whitelist in the Available Definitions section.
  1. Click the right arrow to move the definition(s) to the Added Definitions section. (To remove a definition from the whitelist, select it in the Added Definitions section and click the left arrow).

Use an IP-blocking directive to block groups of IP addresses. You can also specify IP addresses to whitelist.
  1. From the Add Settings list, select IP Blocking.
my services caching add configuration property selected add match rule add setting ip blocking
  1. In the Available Definitions section, select one or more definitions you want to apply to this directive.
  1. Click the right arrow to move the definition(s) to the Added Definitions section. (To remove a definition from the directive, select it in the Added Definitions section and click the left arrow).
  1. Select the radio button for action you want the CDN to take when the match is made: Allow or Deny.
  1. If you selected Deny, select whether you want to display an error or to redirect the request. If you select Redirect, type the destination in the Redirect URL field.

  1. From the Add Settings list, select Lua Scripting.
my services caching add configuration property selected add match rule add setting lua scripting
  1. In the Available Definitions section, select one or more definitions you want to apply to this directive.
  1. Click the right arrow to move the definition(s) to the Added Definitions section. (To remove a definition from the directive, select it in the Added Definitions section and click the left arrow).

By default, the Lumen CDN includes any query string parameters are honored in the request URL as part of an object cache key. Set Query String Handling to Ignore to signify that all query string parameters present in the request URL should be disregarded when looking in the cache for the object.
  1. From the Add Settings list, select Query String Handling.
my services caching add configuration property selected add match rule add setting query string handling
  1. Select the radio button for how to process query strings: Honor or Ignore.

Use a request-headers directive to tell the CDN when (and which) custom HTTP request header definition to send upstream to the origin.

  1. From the Add Settings list, select Request Headers.
my services caching add configuration property selected add match rule add setting request header
  1. In the Available Definitions section, select one or more definitions you want to apply to this directive.
  1. Click the right arrow to move the definition(s) to the Added Definitions section. (To remove a definition from the directive, select it in the Added Definitions section and click the left arrow).

Use a response-headers directive to tell the CDN when (and which) custom HTTP response header definition to use.

  1. From the Add Settings list, select Response Headers.
my services caching add configuration property selected add match rule add setting response header
  1. In the Available Definitions section, select one or more definitions you want to apply to this directive.
  1. Click the right arrow to move the definition(s) to the Added Definitions section. (To remove a definition from the directive, select it in the Added Definitions section and click the left arrow).

Use a secure-fill directive to configure full, end-to-end secure fill of your content. (By default, all intra-CDN communication is not secured (over HTTP), regardless of the client protocol and origin fill policy.)

  1. From the Add Settings list, select Secure Fill.
my services caching add configuration property selected add match rule add setting secure fill
  1. Select whether to turn secure fill on or off when the path is met.

Use a secure-fill directive to configure full, end-to-end secure fill of your content. (By default, all intra-CDN communication is not secured (over HTTP), regardless of the client protocol and origin fill policy.)
  1. From the Add Settings list, select Stale Content Control.
my services caching add configuration property selected add match rule add setting stale content control
  1. If you want the CDN to immediately return a stale response while it revalidates the stale content in the background, click the stale-while-revalidate checkbox. (When you click the checkbox, the CDN returns cached, but stale, content to the client while revalidating the object in the background for the next request.)
  1. If you want the CDN to return a stale response when it receives an error (such as a 500 Internal Server Error or DNS failure), click the stale-if-error checkbox, then select the checkbox for types of errors you want this to apply for: 4xx errors, 5xx errors, or both.

Use a token-authentication directive to authenticate requests for protected content. You can also set the response the CDN returns to a client whose access is being denied due to the applied token policy—and you can set the response to either an error (403 response) or a redirect to another site (typically used to explain to the user why they are being denied access). You can also specify IP addresses to whitelist (bypassing the token authentication).
  1. From the Add Settings list, select Token Authentication.
my services caching add configuration property selected add match rule add setting token authentication
  1. In the Available Definitions section, select one or more definitions you want to apply to this directive.
  1. Click the right arrow to move the definition(s) to the Added Definitions section. (To remove a definition from the directive, select it in the Added Definitions section and click the left arrow).
  1. Repeat step 6 to add additional match rules.
  1. If you need to edit or add other definitions or properties, continue editing the configuration without saving. (Saving the configuration creates a new version.) When you're done editing the configuration, continue with step 9.
  1. Click Save (above the Service-Wide Definition section). You can also click Save As to save the configuration under a new name.
my services caching save configuration save as.
  1. If needed, add any notes to describe the changes you made.
  1. Click Save again.

    Media portal saves the configuration.