Query-String Caching controls how files are to be cached when they contain query strings. Three different modes available, and they are as follows:
"standard-cache": This is the default mode, in which all query strings for a given URL map to the cache file. The file is cached as if there were no query string present: /a.js?v=1 and /a.js?v=2 and /a.js all map to the same cache file. Note however that whenever a cache server must contact an origin server, either on a cache miss or to revalidate an expired cache file, the full query string (if any) from the current end-user request is passed along to the origin server.
"no-cache": In this mode, any URLs containing query strings are not cached and always result in a proxy request to the origin server.
"unique-cache": In this mode, each unique query string maps to a unique cache file; /a.js?v=1 and /a.js?v=2 and /a.js all map to different cache files (even if some of them ultimately have the same content). If you use this mode, we recommend that you also enable query-string logging in the query-string logging page.
*IMPORTANT NOTE* This mode should not be used when the query string contains parameters that will change with every request, such as a session id or a user name, since this would result in a very low cache hit ratio. If token auth is enabled, query-string caching can not be enabled.
standard-cache
no-cache
unique-cache