gy1082 opened a new issue, #12166: URL: https://github.com/apache/trafficserver/issues/12166
Description: Traffic Server's read-while-write pattern is broken for concurrent requests to expired cached resources when the origin content is unmodified. The issue stems from IMS (If-Modified-Since) header removal in handle_cache_write_lock() during cache write lock failures. When multiple concurrent requests arrive for an expired cached resource where the origin content hasn't been modified: 1. First request attempts to get a write lock for cache update 2. Concurrent requests fail to get the write lock (CACHE_WL_FAIL) 3. IMS headers are removed from these concurrent requests 4. Each concurrent request makes a separate origin request 5. Requests are logged as TCP_REFRESH_MISS This behavior causes unnecessary load on origin servers and defeats the purpose of the read-while-write pattern. Question: For this specific scenario, can we preserve the IMS headers even during cache write lock failures? This would help maintain proper read-while-write functionality and prevent redundant origin requests when we know the resource hasn't been modified. Version: Apache Traffic Server 9.2.3 -- 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: issues-unsubscr...@trafficserver.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
