You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@trafficserver.apache.org by "Leif Hedstrom (JIRA)" <ji...@apache.org> on 2013/05/04 03:03:13 UTC

[jira] [Updated] (TS-1702) enable_read_while_writer on with simultaneous cache entry refreshes can leak 304's to client

     [ https://issues.apache.org/jira/browse/TS-1702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Leif Hedstrom updated TS-1702:
------------------------------

    Labels: A  (was: )
    
> 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
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira