[jira] [Updated] (TS-2912) HEAD transaction on stale entry deletes cache entry

2014-07-03 Thread Leif Hedstrom (JIRA)

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

Leif Hedstrom updated TS-2912:
--

Fix Version/s: 5.1.0

> HEAD transaction on stale entry deletes cache entry
> ---
>
> Key: TS-2912
> URL: https://issues.apache.org/jira/browse/TS-2912
> Project: Traffic Server
>  Issue Type: Bug
>  Components: HTTP
>Reporter: William Bardwell
> Fix For: 5.1.0
>
>
> On a stale cache entry a HEAD gets tunneled to the origin, but when a 200 
> comes back 
> HttpTransact::handle_cache_operation_on_forward_server_response(State* s)
> deletes the cache entry, it seems like it should just ignore it (or check 
> ETag/Last-Modified and maybe delete if those don't match, but not 
> unconditionally.)
> I am seeing this with 4.2.X with a plugin fiddling with stuff, but the code 
> looks the same in trunk, line 4318 looks like the problem line.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Updated] (TS-2912) HEAD transaction on stale entry deletes cache entry

2014-07-04 Thread weijin (JIRA)

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

weijin updated TS-2912:
---

Attachment: ts-2912.try1.diff

@William Bardwell, [~zwoop]
I wrote a patch to solve the bug, please review it if you have time.

> HEAD transaction on stale entry deletes cache entry
> ---
>
> Key: TS-2912
> URL: https://issues.apache.org/jira/browse/TS-2912
> Project: Traffic Server
>  Issue Type: Bug
>  Components: HTTP
>Reporter: William Bardwell
>Assignee: weijin
> Fix For: 5.1.0
>
> Attachments: ts-2912.try1.diff
>
>
> On a stale cache entry a HEAD gets tunneled to the origin, but when a 200 
> comes back 
> HttpTransact::handle_cache_operation_on_forward_server_response(State* s)
> deletes the cache entry, it seems like it should just ignore it (or check 
> ETag/Last-Modified and maybe delete if those don't match, but not 
> unconditionally.)
> I am seeing this with 4.2.X with a plugin fiddling with stuff, but the code 
> looks the same in trunk, line 4318 looks like the problem line.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Updated] (TS-2912) HEAD transaction on stale entry deletes cache entry

2014-08-01 Thread Leif Hedstrom (JIRA)

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

Leif Hedstrom updated TS-2912:
--

Labels: review  (was: )

> HEAD transaction on stale entry deletes cache entry
> ---
>
> Key: TS-2912
> URL: https://issues.apache.org/jira/browse/TS-2912
> Project: Traffic Server
>  Issue Type: Bug
>  Components: HTTP
>Reporter: William Bardwell
>Assignee: weijin
>  Labels: review
> Fix For: 5.1.0
>
> Attachments: ts-2912.try1.diff
>
>
> On a stale cache entry a HEAD gets tunneled to the origin, but when a 200 
> comes back 
> HttpTransact::handle_cache_operation_on_forward_server_response(State* s)
> deletes the cache entry, it seems like it should just ignore it (or check 
> ETag/Last-Modified and maybe delete if those don't match, but not 
> unconditionally.)
> I am seeing this with 4.2.X with a plugin fiddling with stuff, but the code 
> looks the same in trunk, line 4318 looks like the problem line.



--
This message was sent by Atlassian JIRA
(v6.2#6252)