Overview
Cache Keys allow you to cache additional versions of a file for end-users that may request them.
Cache Key Modification
The Cache Key Modification policy allows for manipulation of the way the cache uniquely stores assets.
Case Insensitive Cache
When enabled, the path portion of the cache key will be normalized to lower case. So a client request or a purge for /PaTh/To/FiLe.TxT will have a cache key of path/to/file.txt. We will still pass the original request through to the origin, unaltered. This only applies to the path and not the query string.
includeOriginPullProtocol
When enabled, this setting will include the OriginPull protocol as part of the cache key. The CDN will assume the origin would return a different response based on the OriginPull protocol (HTTP or HTTPS).
Dynamic File Versioning
You can specify which parts of the end-user request should be used to build additional cache keys. Different parameters or headers will cause different versions of a file to be cached.
Additional Cache Keys By Headers
You can compile a list of headers to use as independent cache keys.
Additional Cache Keys By Query String Parameters
You can compile a list of query string parameters to use as additional cache keys.
Please note that negative pattern matching is not supported.