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.
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).
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.)
Use a deny-policy directive to reject or redirect (to an alternate URL) all requests matching specific criteria.
Use the cache-control directive to set the internal and external caching policy. The internal policy tells the CDN how it should cache the object; the external policy instructs the CDN on what information to include in the response sent to the client, influencing how the client caches the received content.
By default, the CenturyLink 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.
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).
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.
Use an IP-blocking directive to block groups of IP addresses. You can also specify IP addresses to whitelist.
Use a request-headers directive to tell the CDN when (and which) custom HTTP request header definition to send upstream to the origin.
Use a response-headers directive to tell the CDN when (and which) custom HTTP response header definition to use.
7. Repeat step 6 to add additional match rules.
8. 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.
9. Click Save (above the Service-Wide Definition section). You can also click Save As
to save the configuration under a new name.
10. If needed, add any notes to describe the changes you made.
11. Click Save again.
Media portal saves the configuration.