AIO Runtime Caching Configuration- With Cache-Control Header is not working | Community
Skip to main content
banerjee_ronit
November 2, 2021
Solved

AIO Runtime Caching Configuration- With Cache-Control Header is not working

  • November 2, 2021
  • 2 replies
  • 2072 views

I am willing to configure caching for my IO Runtime action using the Cache Control Header - Cache-Control:max-age=1800.

Although the header is coming up in response, but the action is not hitting the cache on subsequent calls. 

Also the header X-Cache is CONFIG_NOCACHE , which signifies that Caching has not been configured from Azure CDN (Note that IO runtime is internally leveraging MS Azure) 

Is there any thing else that needs to configured for this to work?

Below are the cache related headers which I am currently getting as part of IO Action response:

Cache-Control: max-age=1800

X-Cache:CONFIG_NOCACHE

x-gw-cache:BYPASS

 

Thanks and regards,

Ronit Banerjee.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by duynguyen_adobe

@banerjee_ronit - how are you inspecting the request? using Postman?

Please make sure that you un-check "disable cache" in Postman settings (which is checked by default).

And also you should make a GET call, not POST.

2 replies

banerjee_ronit
November 2, 2021

   @duynguyen_adobe   - Any insights/suggestions on the above would be of great help. 

duynguyen_adobeAdobe EmployeeAccepted solution
Adobe Employee
November 2, 2021

@banerjee_ronit - how are you inspecting the request? using Postman?

Please make sure that you un-check "disable cache" in Postman settings (which is checked by default).

And also you should make a GET call, not POST.

banerjee_ronit
November 2, 2021

@duynguyen_adobe  - Tested from browser (GET call) and its working. Thanks!