[jira] [Updated] (TS-4774) proxy.config.http.cache.open_write_fail_action=2 doesn't work

["Leif Hedstrom (JIRA)" <ji...@apache.org>]

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

Leif Hedstrom updated TS-4774:
------------------------------
    Fix Version/s:     (was: 7.0.0)
                   7.1.0

> proxy.config.http.cache.open_write_fail_action=2 doesn't work
> -------------------------------------------------------------
>
>                 Key: TS-4774
>                 URL: https://issues.apache.org/jira/browse/TS-4774
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: Core
>            Reporter: James Peach
>              Labels: A
>             Fix For: 7.1.0
>
>
> If you set {{proxy.config.http.cache.open_write_fail_action=2}} there is no change of behaviour.
> If you just do a {{GET}} on a stale object, the root cause of this is that {{OverridableHttpConfigParams::cache_open_write_fail_action}} is never copied to {{HttpTransact::State::cache_open_write_fail_action}} when this is checked. If you fix this, then it always returns a stale object without revalidating.
> If you cause the object to be locked in the cache by doing a {{GET}} that takes a long time to return, a second lookup goes direct to origin and the {{cache_open_write_fail_action}} is never checked.



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