HTTP Rules Engine can be used to override and/or extend the CDN configuration defined in the MCC and the response headers defined by a web server (e.g., Apache or IIS).
- Web Server (Customer Origin): A web server can define key response headers that will be associated with assets requested through our CDN. For example, a web server can define response headers that control the cache policy for requested assets. HTTP Rules Engine allows you to override those response headers to create a custom cache policy for content served through the CDN.
- Default CDN Response Headers: If certain key response headers have not been defined by the origin server, then a default response header value may be assigned to the cached asset and the response returned to the user agent. These default response header values can also be overridden by HTTP Rules Engine.
- MCC: The MCC allows you to define how assets can be accessed through the CDN. HTTP Rules Engine can be used to customize the actions that will take place when content is requested on your account. For example, you can create a rule that prevents users from a particular country or region from requesting content from a customer origin.
HTTP Rules Engine also allows you to override an existing CDN configuration. For example, you can create a rule that disables Token-Based Authentication for all HTML assets. This type of rule would bypass the check for Token-Based Authentication even when the requested HTML assets are in a secured directory. Keep in mind that this scenario will still require valid tokens for any supporting assets for that HTML page (e.g., JS, CSS, images, etc.) that reside in a location secured by Token-Based Authentication.
The following illustration is of a rule that disables Token-Based Authentication for HTML files.
