Diese Konversation wurde aufgrund von Inaktivität geschlossen. Bitte erstellen Sie einen neuen Post.
Level 1
Level 2
Melden Sie sich an, um alle Badges zu sehen
Diese Konversation wurde aufgrund von Inaktivität geschlossen. Bitte erstellen Sie einen neuen Post.
I am using the ACS Commons Dispatcher TTL feature to set max-age headers to certain requests. I've also configured a list of query parameters which are ignored by Dispatcher. Both of these are working as expected. However, if a request is made to a page that contains ignored query parameters, then the page becomes cached in Dispatcher, but with no max-age header. This appears to be expected behaviour for the ACS Commons Dispatcher TTL feature, so what is the best way to ensure that requests that contain ignored query parameters can still be cached in Dispatcher with a max-age header?
EDIT: This unwanted behaviour only occurs if a request is made to a page that has not yet been cached in Dispatcher (or the cache has expired), and the request contains query parameters on the list of ignored query params, so that Dispatcher still creates the cache file, but no max-age header is added by the ACS Commons code.
Anhand von Themen werden Community-Inhalte kategorisiert und Sie können so relevanten Inhalt besser finden.
Zugriffe
Antworten
Likes gesamt
Have you enabled the TTL? Does is your response headers for caching setup?
Take a look at these configurations in the dispatcher.any file.
Example of enabled cache-control cached header, and enabled TTL on the dispatcher.any file:
# Cache response headers next to a cached file. On the first request to
# an uncached resource, all headers matching one of the values found here
# are stored in a separate file, next to the cache file. On subsequent
# requests to the cached resource, the stored headers are added to the
# response.
#
# Note, that file globbing characters are not allowed here.
#
/headers
{
"Cache-Control"
"Content-Type"
"Last-Modified"
}
# Enable TTL evaluates the response headers from the backend, and if they
# contain a Cache-Control max-age or Expires date, an auxiliary, empty file
# next to the cache file is created, with modification time equal to the
# expiry date. When the cache file is requested past the modification time
# it is automatically re-requested from the backend.
#
/enableTTL "1"
Zugriffe
Antworten
Likes gesamt
Zugriffe
Antworten
Likes gesamt
Hi, I am also facing the same issue. Did you find any solution for this ?
Zugriffe
Antworten
Likes gesamt
Zugriffe
Likes
Antworten
Zugriffe
Likes
Antworten
Zugriffe
Likes
Antworten
Zugriffe
Like
Antworten