Please refer below URLs for caching requests with query param :
- https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/how-dispatcher-caches-page...
>> This can only return a single cached page
- https://one-inside.com/caching-pages-with-suffix-paths-in-aem-cq-dispatcher/
>> This appears to require significant customisation which also doesn't work OOTB.
To add to it, you can't really use query parameters if you want to cache distinct pages. "Ignore" tells Dispatcher to ignore the parameters which means it always returns the same cached result from the first call (with whatever parameters where there).
The "AEM" Style of parameters would be to encode the parameterized data into a suffix in the code that's calling the URL,
instead of foo.html?category=1234&product=9876 like so:
foo.html/category/1234/product/9876
or you encode the data somehow into selectors:
foo.cat_1234.prod_9876.html
If you don't have control over the requesting client, you can cache in the Publish with something like the EHCache framework (a bit slower than in Dispatcher)
Theoretically - though it can become very complicated - you should be able to write a regex that is doing the mapping from query parameter to selectors on the fly - though I would strongly discourage that, as this is not a clean design (and I haven't tried it myself)
One additional point to consider:
foo.html/category/1234/product/9876 the suffix would still require an extension in order for it to be cached, ie: foo.html/category/1234/product/9876.html or foo.json/category/1234/product/9876.json
Do not use ".html" as an extension when you have a suffix. (Or do not use any extension with and without suffix in the same project).
See "Conflicting Suffix URLs" in https://experienceleague.adobe.com/docs/experience-manager-learn/dispatcher-tutorial/chapter-1.html for details So the correct example would be something like
foo.detail/category/1234/product/9876.html ^^^^^^
