[AMS Dispatcher] A new flush vhost to invalidate author cache #1038
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
The PR adds a new vhost to invalidate cache on author dispatcher in AMS setups.
Related Issue
#1037
Motivation and Context
The current AMS Dispatcher configuration does not provide a way to flush cache on author dispatcher. Flush requests always resolve to a publisher farm which invalidates content in publisher document root.
The PR adds a new "authorflush" vhost which resolves to the author farm. To use it from AEM you'd need to define a new Flush agent and set
authorflush
in the Host header:How Has This Been Tested?
In our setup we use the Dispatcher Flush UI tool, but the problem is also reproducible from curl. Execute the commands below while tailing dispatcher.log :
Current behaviour using the default "flush" vhost.
dispatcher resolves publishfarm and invalidates publish docroot (
/mnt/var/www/html
)The fixed behaviour using the new "authorflush" vhost.
dispatcher resolves authorfarm and invalidates publish docroot (
/mnt/var/www/author
)Screenshots (if appropriate):
Types of changes
Checklist: