In the release notes for Dispatcher v4.3.3, it mentions an improvement:
Does anyone know what this improvement actually does? We are trying to use the Apache mod_headers to add Cache-Control to certain responses, but it does not work if the request contains query parameters. If we remove the query parameters from the request, or we change the cache-control header to another header (like cache-control2) then it works.
Solved! Go to Solution.
Views
Replies
Total Likes
May want to log a ticket.
DISP-818 removed the Cache-Control header from requests with query parameters
BUT -- this introduced some unintended things which are currently being handled under the open JIRA GRANITE-29891
Actually the mod_expires always added headers to any response, even if this response was supposed to be uncacheable.
And technically (according to the RFCs) any request containing a query string must not be cached.
HTH,
Jörg
Views
Replies
Total Likes
@Jörg_HohIn my case it is still not adding Cache-Control for uncacheable (denied in cache.any) request.
I have used
ExpiresByType application/javascript "access plus 1 month"
But as soon as I add the entry to deny caching, the Cache-Control header gets removed from the final response.
Views
Replies
Total Likes
Views
Replies
Total Likes
@Jörg_Hoh Yes, we are trying to add cache-control: max-age=0, no-cache, no-store, must-revalidate to the response so that the CDN does not cache the page, but the cache-control header is missing from the response when we try to set it using the Header directive.
Views
Replies
Total Likes
May want to log a ticket.
DISP-818 removed the Cache-Control header from requests with query parameters
BUT -- this introduced some unintended things which are currently being handled under the open JIRA GRANITE-29891