By default, cache keys are generated under the assumption that path and filename components are case-sensitive, so that File.​html and file.​html use separate cache keys. Enabling this behavior forces URL components whose case varies to resolve to the same cache key. Enable this behavior if your origin server is already case-insensitive, such as those based on Microsoft IIS.

With this behavior enabled, make sure any child rules do not match case-sensitive path components, or you may apply different settings to the same cached object.

Note that if already enabled, disabling this behavior potentially results in new sets of cache keys. Until these new caches are built, your origin server may experience traffic spikes as requests pass through. It may also result in cache pollution, excess cache space taken up with redundant content.

If you're using Net​Storage in conjunction with this behavior, enable its Force Case option to match it, and make sure you name the original files consistently as either upper- or lowercase.


Ignores case when forming cache keys.