Azure API Management caching optimization guide as expected with backend service
I'm collaborating on a project where I tried several approaches but none seem to work. I'm trying to implement caching in Azure API Management (APIM) for my backend service, but it doesn't seem to be working as I expected. I've set up a policy to cache responses from my Azure Function, but when I make subsequent calls to the API, I'm always getting a fresh response from the backend instead of the cached one. Here's the policy I'm using: ```xml <policies> <inbound> <base /> <set-cache-configuration duration="60" /> </inbound> <backend> <base /> </backend> <outbound> <base /> <cache-lookup /> <set-header name="Cache-Control" exists-action="override"> <value>public, max-age=60</value> </set-header> </outbound> </policies> ``` I've tested this with both the Azure Function running directly and through APIM, and I'm not seeing any cache hits. I've also checked that the function response headers do not contain `Cache-Control: no-cache` or similar directives that would prevent caching. I've also tried increasing the duration in the `set-cache-configuration` policy to see if that made a difference, but it didn't change the behavior. Additionally, I confirmed that the caching is enabled in the APIM settings. Is there something I'm missing in the policy setup that could be causing the cache to bypass or not store the response? Any insights or best practices for debugging caching issues in Azure API Management would be greatly appreciated! I'm working in a Windows 10 environment. Any pointers in the right direction? I'm developing on Linux with Xml. How would you solve this?