This change allows you to match the current hash or timestamp in the URL route. Kind of an edge case for CDN origin servers, but putting the hash in the URL path guarantees that the current asset is served correctly during staggered releases across multiple load-balanced hosts, rather than relying on cache-invalidation with GET parameters.
This change allows you to match the current hash or timestamp in the URL route. Kind of an edge case for CDN origin servers, but putting the hash in the URL path guarantees that the current asset is served correctly during staggered releases across multiple load-balanced hosts, rather than relying on cache-invalidation with GET parameters.