We have a requirement where in we want to cache the servlet(AEM) response.
Servlet is making a REST call to third party to fetch a response which is constant(response remains same)
Response of the servlet to be cached:
Servlet : /bin/servletpathname?queryParam=apiurl.
From clientside, we are making an ajax call to /bin/servletpathaname/apiurl/a.html (a.html is being appended so that the request has an extension.).
At Dispatcher We
are using internal redirect to redirect /bin/servletpathaname/apiurl/a.html to /bin/servletpathname?queryParam=apiurl.
We are able to get a successful response back from servlet (Internal Redirect is successful). But at dispatcher we observe that the request is not getting cached.
Am I missing something?
I want to understand how can we cache the servlet response, this would greatly reduce the load on the end server and improve performance.
> At Dispatcher We are using internal redirect to redirect /bin/servletpathaname/apiurl/a.html to /bin/servletpathname?queryParam=apiurl.
That will not make the request cacheable unfortunately, dispatcher will not cache 301 or 302 redirects or requests that it must send with a querystring. Even though you are rewriting this or redirecting this at the Apache level you cannot cache it in dispatcher unless you create a mapping in AEM that maps from /bin/servletpathaname/apiurl/a.html to /bin/servletpathname?queryParam=apiurl. Alternatively, you could cache these requests at the CDN level. Many CDNs do allow caching of requests with querystrings.
Note: The request received by Apache here is the /bin/servletpathaname/apiurl/a.html one, but the request being received and sent by the dispatcher module within apache has the querystring: /bin/servletpathname?queryParam=apiurl
Hi , Since in your case getting the same response always ,
Instead of using query params, you can also try selectors like /bin/servletpathaname/a.apiurl.html in Ajax call. Later you can read this selector in servlet , by this you can cache the response.
We are fetching articles from 3rd party system via REST API calls. The frequency of this content getting modified is very less. Within AEM, content author would then author the component with the Article API call. This API is forwarded to dispatcher as apiurl in below url.
/bin/servletpathaname/apiurl/a.html. We have a rewrite rule at dispatcher to send the servlet as /bin/servletpathname?queryParam=apiurl. Servlet would then make the call to thirdparty system( we are trying to minimize these calls)
When an enduser hits the page, if we have the servlet response cached we can render that from dispatcher instead of hitting third party system( they have concerns over the traffic to their system).