bneradt commented on PR #13417: URL: https://github.com/apache/trafficserver/pull/13417#issuecomment-5500318690
Addressed the remaining review issue and force-pushed `18e63ce1c8`. Write-side freshness limits are now kept pending separately for the original and transformed cache objects. `cfl` is published only after `tunnel_handler_cache_write()` reports a successful write; failures discard the pending value without overwriting freshness information for a cached object already selected for serving. If both object variants succeed, the transformed object retains precedence. I also added deterministic failed-write coverage by exceeding `proxy.config.cache.max_doc_size`. The replay verifies that the write result is `ERR` and both `cfl` and `cca` remain `-1`; the existing successful-write, hit, negative-revalidation, and non-cacheable cases still pass. Validation in `asfats5`: - Full configure, format, build, and install: passed. - Focused `cache-freshness-fields` AuTest: passed. -- 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]
