Caching vanity url's in dispatcher. | Community
Skip to main content
sgarg122001
sgarg122001
Level 2
August 11, 2018
Solved

Caching vanity url's in dispatcher.

  • August 11, 2018
  • 3 replies
  • 3539 views

Hi All,

Can you please explain and share some updated document that how the caching can be done for vanity url's and also how the cache will be invalidate on page activation for vanity url enabled pages. We have the centralized location for vanity url's and same path we have mentioned in dispatcher file to access those vanity url's.

Thanks

Sahil Garg

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

3 replies

sgarg122001
sgarg122001Author
Level 2
August 12, 2018

hi Arun,

Thanks for reply!!!!

Is it mean dispatcher will cache the vanity url's on there own and to invalidate that we have to make changes under the replication agent?

Or do we need to make some configuration changes to cache the vanity url's.

Thanks in Advance.

arunpatidar
Community Advisor
arunpatidarCommunity Advisor
Community Advisor
August 12, 2018

Hi,

Dispatcher cache everything except a document in the following circumstances:

  • If the request URI contains a question mark ("?").
  • This usually indicates a dynamic page, such as a search result that does not need to be cached.
  • The file extension is missing.
    The web server needs the extension to determine the document type (the MIME-type).
  • The authentication header is set (this can be configured)
  • Methods other than GET or HEAD (for the HTTP header) are not cacheable by the Dispatcher by default.
  • If the AEM instance responds with the following headers:
    • no-cache
    • no-store
    • must-revalidate
Arun Patidar
Terms & ConditionsAccessibility statement

Loading footer...