You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Sudheer Vinukonda (JIRA)" <ji...@apache.org> on 2015/08/28 17:02:46 UTC
[jira] [Updated] (TS-3872) Enhance open_write_fail_action feature
to support returning error on revalidation.
[ https://issues.apache.org/jira/browse/TS-3872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sudheer Vinukonda updated TS-3872:
----------------------------------
Assignee: Sudheer Vinukonda
Affects Version/s: 6.1.0
Fix Version/s: 6.1.0
> 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)