Github user mlibbey commented on the issue:
https://github.com/apache/trafficserver/issues/1626
Don't get this sentence:
> If it is enabled, than caching the negative response, the current
(possibly stale) content is preserved and served.
I think this should only be in play for stale content -- wouldn't be
revalidating fresh content, right? Perhaps
If it is enabled, rather than caching the negative response, the current
stale content is preserved and served.
> If the origin provides a valid response that is not considered a failure
in this context.
Perhaps missing a comma after response?
Would a 5xx error be considered a valid response? We use cache hierarchies
extensively, and this setting kicks in when our parents return a 5xx error to
the children. Perhaps 'a valid response specific to the object'?
proxy.config.http.negative_revalidating_lifetime
appears to be both reloadable and overridable.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
