Dispatcher none status

[fcondomitti]

Morning,

we have both an infrastructure consisting of dispatcher and publish instance on the same machine, and in two separate machines.

In both configurations however one and only one call to a specific servlet, even if it's cached, when called from another linux machine and not from the browser does not return the cached json data, but executes the whole servlet. Inspecting the dispatcher logs, instead of the hit/miss status I see none.

No dynamic parameters are passed in the call. Can you explain me the meaning of "none"?

Thanks a lot

[arunpatidar]

Can you check the cache header?

the cache-action here is NONE, this means that this request will not be cached in the Dispatcher.

You can enable the debug log and check the issue

https://blogs.perficient.com/2017/10/12/mastering-aem-dispatcher-part-1-debugging-the-dispatcher/

[fcondomitti]

Thanks @arunpatidar.

I set the dispatcher log level at DEBUG, and as you said I found:

cache-action for [/content/common-content.features.all.json]: NONE
Adding request header: X-Forwarded-Proto
Adding request header: user-agent
Adding request header: accept-encoding
Adding request header: accept
Adding request header: host
Adding request header: Via
Adding request header: X-Forwarded-For
Adding request header: Server-Agent

When called from the browser the cache-action is DELIVER, since the file is cached. How is this cache-action set and where can I intervene?

[Himanshu_Jain · Accepted solution]

Check https://experienceleague.adobe.com/docs/experience-manager-dispatcher/using/configuring/dispatcher-c...