traeak opened a new pull request, #12092: URL: https://github.com/apache/trafficserver/pull/12092
relates to issue #12047 With the slice plugin when an asset goes stale in cache and an IMS request results in a 304, the slice plugin may end up causing each range request to perform an IMS request, get a 304 and write another header into the cache just for that range. To get around this the slice plugin will take the strongest identifier from the first range request response and attach and identifier header to the cache_range_requests plugin. If during cache lookup the CRR plugin finds that the resulting asset is stale, it will check the provided identifier against the "stale" slice and will flip it back to "fresh" if the identifiers match. The identifier will be passed as header, with Etag being preferred over Last-Modified. X-Crr-Ident: Etag <etag> or X-Crr-Ident: Last-Modified <last modified> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
