Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

Caching vanity url's in dispatcher.

Avatar

Level 2

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

1 Accepted Solution

Avatar

Correct answer by
Community Advisor
3 Replies

Avatar

Correct answer by
Community Advisor

Avatar

Level 2

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.

Avatar

Community Advisor

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