Multiple Origin Requests Due to Cache Write Lock Failure

Description:
When multiple concurrent requests are made for the same expired cached resource, and the origin content hasn't been modified:

1. Current behavior:
- The handle_cache_write_lock function removes the IMS (If-Modified-Since) header
- This results in multiple origin requests for the same resource
- These requests are logged with TCP_REFRESH_MISS status

Question:
For this specific scenario where concurrent requests are made for an expired cached resource and the origin content hasn't been modified, can we preserve the IMS headers in handle_cache_write_lock? This would potentially reduce unnecessary origin requests.

Version: Apache Traffic Server 9.2.3