Which page will be cached on the dispatcher?

Given this configuration property:

Which page will be cached on the dispatcher?
A . /myproduct/myrecipe. htmI’search=searchparam
B . /myproduct/myrecipe. html?search- s&ordet=asc&brand=ad
C . /myproduct/myrecipe. html?brand=mybrand

View Answer

Answer: C

Explanation:

Given the dispatcher configuration snippet provided in the image, we can understand the URL

patterns that will be ignored (not cached) by the dispatcher. The configuration under /ignoreUrlParams shows patterns to match query parameters in the URLs:

/0001 { /glob "*" /type "deny" } means that by default, all query parameters are ignored (not cached).

/0002 { /glob "search" /type "allow" } specifically allows caching for URLs with the ‘search’ parameter.

/0003 { /glob "order" /type "allow" } specifically allows caching for URLs with the ‘order’ parameter.

Based on this, let’s evaluate the options:

A) /myproduct/myrecipe.html?search=searchparam ― This URL will not be cached because the ‘search’ parameter is allowed, but the actual value ‘searchparam’ does not match any allow pattern.

B) /myproduct/myrecipe.html?search=s&order=asc&brand=ad ― This URL will not be cached because although ‘search’ and ‘order’ parameters are allowed, the ‘brand’ parameter is not allowed according to the configuration.

C. /myproduct/myrecipe.html?brand=mybrand ― This URL will be cached because there are no allowed parameters, so the default deny does not apply, and the page can be cached without considering the ‘brand’ parameter.

Therefore, the page that will be cached on the dispatcher is the one in option C, as it does not contain any of the explicitly allowed query parameters (‘search’ or ‘order’), and all other parameters are ignored by default.