traeak commented on issue #12047: URL: https://github.com/apache/trafficserver/issues/12047#issuecomment-2697837803
I think what's happening is that each slice of that asset is having to handle and store the 304 response. In the general case I'm not sure how to get around that since individual slices of the same asset name might have different content from multiple different versions of the named asset. A possible solution: Use a reference slice. That should always have the most up to date etag/last-modified "variant identifier" (or whatever it's called). Pass this reference slice etag/last-modified "variant identifier" to subsequent calls of the CRR plugin. If the CRR plugin encounters a STALE in-cache result (from cache read hook) but the variant identifier matches, switch to FRESH and continue. This should stop the CRR plugin from going to parent and also should result in having a variant header being written to cache. I think. -- 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]
