[
https://issues.apache.org/jira/browse/TS-3872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14719311#comment-14719311
]
ASF subversion and git services commented on TS-3872:
-----------------------------------------------------
Commit 4f2967e9fef7a44f2db7c9a551a3ce39fc9ae4b6 in trafficserver's branch
refs/heads/master from [~sudheerv]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=4f2967e ]
[TS-3872] Minor doc fixup.
> 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
> Reporter: Sudheer Vinukonda
>
> 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)
