Lumen help
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:
Any operator may be inverted by prepending an “!” (not).
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.
Use a deny-policy directive to reject or redirect (to an alternate URL) all requests matching specific criteria.
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.
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.)
Learn more about
Media portal
Explore Media portal
Top 10 articles