You can choose to or not to ignore the letter case of client request URLs as needed to optimize the node cache and load requested resources more quickly.
When a node responds to a resource request, it will use the complete request URL as the cache key to match the cached resource and follow the letter case of the original request URL. Even if URLs in different letter cases have the same content, they will match different node caches. For example,
https://www.example.com/images/demo.jpg will be identified as different resource requests. If the resource is not on the node, the request will be forwarded for origin-pull, which increases the origin-pull traffic.
demo.jpg does not vary by letter case (that is, even if in different letter cases,
demo.jpg indicates the same image), then you can ignore the letter case to unify the requests to match the same node cache. For example, both
https://www.example.com/images/demo.JPG match the cached resource
Check the impact of the letter case on resources in business resource URLs and use the case ignoring feature to optimize the cache accordingly.
This feature doesn't affect origin-pull request URLs and only changes the cache key of request on nodes. The origin-pull request URLs are the same as the URLs of original requests initiated by clients.