[jira] [Commented] (TS-3872) Enhance open_write_fail_action feature to support returning error on revalidation.

["William Bardwell (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TS-3872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14724593#comment-14724593 ] 

William Bardwell commented on TS-3872:
--------------------------------------

Do any of those options go ahead and do a conditional revalidate (even if they can't save the answer), just passing through the answer if they don't get a 304?  Because that seems like a much better behavior than the old 'tunnel' case (aka 0), but I wasn't clear if one of the other options does that...

> Enhance open_write_fail_action feature to support returning error on revalidation.
> ----------------------------------------------------------------------------------
>
>                 Key: TS-3872
>                 URL: https://issues.apache.org/jira/browse/TS-3872
>             Project: Traffic Server
>          Issue Type: Improvement
>          Components: HTTP
>    Affects Versions: 6.1.0
>            Reporter: Sudheer Vinukonda
>            Assignee: Sudheer Vinukonda
>             Fix For: 6.1.0
>
>
> Refer TS-3549.
> The setting *proxy.config.http.cache.open_write_fail_action* currently supports the below options:
> On a cache write lock failure (multiple concurrent requests for the same object):
> (a) Return a 502 error on cache miss
> (b) Return a stale copy on revalidation
> (c) Both (a) and (b)
> This jira is to add a new option to allow ATS to return a 502 error on both cache miss as well as revalidation scenario.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)