Azure Front Door requires the content-length values to be the same for any GET HTTP request. Range requests may be compressed into different sizes.

The resulting item is returned with a transfer-encoding: chunked.

Afterward, the compressed file is served from the cache. When a request for an asset specifies compression and the request results in a cache miss, Azure Front Door (classic) does compression of the asset directly on the POP server. If a request supports gzip and Brotli compression, Brotli compression takes precedence. These profiles support the following compression encodings: The current list is:Īdditionally, the file must also be between 1 KB and 8 MB in size, inclusive. Currently, Front Door (classic) doesn't allow this list to be changed. In order for a file to be eligible for compression, caching must be enabled and the file must be of a MIME type to be eligible for compression. File compressionĪzure Front Door (classic) can dynamically compress content on the edge, resulting in a smaller and faster response time to your clients. If the backend doesn't support byte-range requests, this optimization isn't effective. This optimization relies on the backend's ability to support byte-range requests. If the chunks aren't all cached, pre-fetching is used to request chunks from the backend. Ensuing requests for the file or byte ranges are served from the cache. This process continues until the entire file gets downloaded (if requested) or the client closes the connection.įor more information on the byte-range request, read RFC 7233.įront Door caches any chunks as they're received so the entire file doesn't need to be cached on the Front Door cache. This pre-fetch ensures that the content stays one chunk ahead of the user, which reduces latency. Front Door then pre-fetches the next chunk in parallel. After receiving a full or byte-range file request, the Front Door environment requests the file from the backend in chunks of 8 MB.Īfter the chunk arrives at the Front Door environment, it's cached and immediately served to the user. When a large file is requested, Front Door retrieves smaller pieces of the file from the backend.

Front Door uses a technique called object chunking. Delivery of large filesĪzure Front Door delivers large files without a cap on file size. Front Door is a modern Content Delivery Network (CDN) with dynamic site acceleration and load balancing, it also supports caching behaviors just like any other CDN. The following document specifies behaviors for Azure Front Door (classic) with routing rules that have enabled caching.

Suitcase fusion 3 clean font cache