Azure Front Door is a global CDN service that enables you to securely expose your web artifacts to the external world. In this short article, I will demonstrate the process of caching and compressing responses by leveraging the caching and compression features provided by Azure Front Door.
It is advisable to apply caching and compression to static files such as CSS, images, JSON files, CSV, etc., as opposed to dynamic content. Therefore, careful route planning is imperative before embarking on the implementation of caching and compression strategies.
Following is an example.
- route 1 - /api/*
- route 2 -/assets/*
Following the example mentioned above, we'll designate the /api route for dynamic API content and the /assets route for static content. Let's proceed with the implementation. Let's focus on /assets route.
Let's start by navigating to the Front Door manager and selecting the desired endpoint.
Click on "Add a route" to begin configuring the routes for your Front Door setup.
Next, specify the path of the route to match
Let's explore how to define cache and compression settings.
I prefer selecting the Use Query String option, as it allows Front Door to independently cache responses with query strings. However, there are other options available for you to choose from.
This completes the necessary steps to optimize your responses for static content.
No comments:
Post a Comment