[
https://issues.apache.org/jira/browse/TS-3993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14989625#comment-14989625
]
Felicity Tarnell commented on TS-3993:
--------------------------------------
Two possible ways I can see to implement this: either add a new config option,
like {{proxy.config.http.cache.purge_invalidates_object}}, or a new request
header to trigger the refresh:
{noformat}
GET / HTTP/1.1
Host: example.com
Cache-Control: x-background-revalidate
HTTP/1.1 202 Accepted
Content-Length: 0
{noformat}
(Or possibly even both.)
> Would like a way to mark cache objects as stale
> -----------------------------------------------
>
> Key: TS-3993
> URL: https://issues.apache.org/jira/browse/TS-3993
> Project: Traffic Server
> Issue Type: Improvement
> Components: Cache
> Reporter: Felicity Tarnell
>
> We use {{stale-if-error}} to return cached content to clients in case of
> origin server failure. However, if an object is removed from the cache by a
> PURGE request, and the origin fails before another client requests the same
> object, an error will be served.
> Instead of using PURGE, we'd like a way to mark the cache item as stale, but
> not delete it, so it will be revalidated on the next request, and if the
> origin is unavailable, it can be served by {{stale-if-error}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
