Azure CDN CONFIG_NOCACHE

@M Fuzail Ahmed ,

Welcome to Microsoft Q&A Platform. Thank you for reaching out & hope you are doing well.

I understand that you've configured caching on your Azure Front Door for one of the URL path with wild card which is accessing the dynamic images from your application, but when you check the browser trace, you see CONFIG_NOCACHE in the response header. You would like to know how to cache the URL path and what could be the reason for not caching it.

Front Door attaches the X-Cache header to all responses.

CONFIG_NOCACHE means request is configured to not cache in the Front Door profile.

Azure Front Door cache behavior and duration can be configured in rules engine. And Rules Engine caching configuration always overrides the route configuration.

1. When caching is disabled, Azure Front Door doesn’t cache the response contents, irrespective of the origin response directives.
2. When caching is enabled, the cache behavior is different depending on the cache behavior value applied by the Rules Engine.

Refer: https://video2.skills-academy.com/en-us/azure/frontdoor/front-door-caching?pivots=front-door-standard-premium#cache-behavior-and-duration

Please check if you have configured any rule set with caching behavior and associated that rule set to your route.

Refer: https://video2.skills-academy.com/en-us/azure/frontdoor/standard-premium/how-to-configure-rule-set

Regards,

Gita

@M Fuzail Ahmed , could you please provide an update on this post?

Thanks for the update. Will check this.

@M Fuzail Ahmed Just checking, let us know if you are still facing this issue. Thank you!

Hello @ChaitanyaNaykodi-MSFT and @GitaraniSharma-MSFT

I'm having a similar issue. I have created a route in my Azure Front Door with specific pattern matches and have enabled caching on this route but notice that I still see CONFIG_NOCACHE for assets that fall within the specific pattern matches. Do I need to apply a rule set on this route in addition to enabling the caching for the route in order to prevent the CONFIG_NOCACHE from happening?