How to disable caching on specific origin with Azure Front Door load balancing?

Question

Hello,

I have configured load balancing on Front Door Origin Group with two origins.

Origin 1 serves as the application, while the Origin 2 serves a maintenance page (simple index-html file) using a storage account (static web). Whenever Origin 1 is deemed unhealthy, requests are routed to Origin 2.

However, I don't want Origin 2 to be cached, so the maintenance page will not continue to be served when Origin 1 is healthy. How can I achieve this if possible?

Thanks.

Answer 1

@Nibbler ,

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

Caching is done at Route and not at Origin Group or Origin.

So caching property cannot be configured for a specific Origin Group or Origin and this property would depend on the route only.

What you can instead do is use Cache-control directives at the "maintenance page" Origin.

• In the AFD, you define the Cache behavior as either "Override if origin missing" or "Honor origin"
• With "Override if origin missing"
  • Don't specify any cache directives in the regular page, let AFD handle it
  • In the maintenance page, specify the cache directives to not cache
• With "Honor origin"
  • In the regular page, specify the cache directives as appropriate
  • In the maintenance page, don't cache
• See :
  • 

Refer : Caching with Azure Front Door

Origins may specify not to cache specific responses using the Cache-Control header with a value of no-cache, private, or no-store. When used in an HTTP response from the origin server to the Azure Front Door POPs, Azure Front Door supports Cache-control directives and honors caching behaviors for Cache-Control directives in RFC 7234 - Hypertext Transfer Protocol (HTTP/1.1): Caching (ietf.org).

Hope this helps.

Thanks,

Kapil

---

Please Accept an answer if correct.

Original posters help the community find answers faster by identifying the correct answer.