[
https://issues.apache.org/jira/browse/TS-1702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Bardwell resolved TS-1702.
----------------------------------
Resolution: Fixed
Fix Version/s: (was: 5.0.0)
4.1.2
The fix to TS-1086 seems to fix this, and is the same underlying issue.
> enable_read_while_writer on with simultaneous cache entry refreshes can leak
> 304's to client
> --------------------------------------------------------------------------------------------
>
> Key: TS-1702
> URL: https://issues.apache.org/jira/browse/TS-1702
> Project: Traffic Server
> Issue Type: Bug
> Components: HTTP
> Affects Versions: 3.2.4, 3.2.0
> Reporter: William Bardwell
> Labels: A
> Fix For: 4.1.2
>
>
> enable_read_while_writer will sometimes fail to get the sort of locks that it
> wants, and will try to send a request forward that is not conditional, but if
> the cache entry content has an ETag and Last-Modified-Time header, then the
> code in HttpTransact::handle_cache_write_lock(State* s) to handle a failed
> write lock will remove the If-Modified-Since but not the If-None-Match. It
> should remove both.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
