Closed NateShaq closed 4 years ago
@NateShaq Thank you for reaching out. We use this platform to improve our documentation. Could you please share the document that you are referring to? We will then investigate and update the thread accordingly.
https://docs.microsoft.com/en-us/azure/frontdoor/front-door-caching
Specifically, the last section titled: "Cache expiration", where Cache-Control response header is being explained.
Azure Mobile Apps Zumo API Version 2.0.0. It was setting the Cach-Control after I was setting it in the context.res header. Everything is all good.
Using Cache-Control: no-store in the response header. Azure Front Door service is still caching. I can add other custom-named headers just fine to the response, but no matter what I try, the Cache-Control response in postman comes back as no-cache even when when the no-store response is set. And I can always see the X-Cache: TCP HITT
This is a node.js express app.
Any thoughts on how to stop caching when I elect to do so within particular requests?