Hi All,
We are using content fragments in our components using asset api. We are directly calling the asset api URL from frontend to get the json for the content fragments. We are trying to cache this json coming from the asset api.
1. We are unable to cache this json in dispatcher as we were receiving pragma: no-cache and
Solved! Go to Solution.
Views
Replies
Total Likes
Create a ResourceChange Listener to the content fragment folder path and clear the dispatcher cache for your servlet path DispatcherFlusher service. Limitation with this approach is dispatcher cache will be removed regardless of any cf get updated under the given path.
What all paths and patterns that you configured in filter? Make sure your content fragment path and extension (json) are targeted in Filter.
I don't think you need to write a servlet again as you already have filter in place.
Whichever way you are handling (Filter/Servlet) to expire the cache the default behavior (flush on publish) will still work. If not working check your dispatcher invalidate rules for your content fragment path.
Views
Likes
Replies