[
https://issues.apache.org/jira/browse/TS-2633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14358893#comment-14358893
]
Sudheer Vinukonda commented on TS-2633:
---------------------------------------
Hi Leif - Yes, assuming that the 406 response doesn't include CC headers that
make it cacheable, TS-3331 should address this bug as well - I think it would
at least, mask it (if not fix the root cause) (since, this bug really seems to
indicate that 406 is being cached despite not being part of the allowed list of
negative responses that can be cached).
> 406 negative responses being cached for too long
> ------------------------------------------------
>
> Key: TS-2633
> URL: https://issues.apache.org/jira/browse/TS-2633
> Project: Traffic Server
> Issue Type: Bug
> Components: Cache
> Affects Versions: 4.0.2
> Reporter: David Carlin
> Assignee: Sudheer Vinukonda
> Labels: yahoo
> Fix For: 6.0.0
>
>
> Settings:
> proxy.config.http.negative_caching_enabled = 1
> proxy.config.http.negative_caching_lifetime = 500
> 406 response is being cached, but lifetime isn't being adhered to. They are
> cached for much longer, perhaps indefinitely. I have seen Age: increase to
> several hours.
> With proxy.config.http.negative_caching_enabled = 0 then 406 responses are
> not cached.
> Bryan pointed out that the docs don't list 406 as one of the cached negative
> responses:
> http://trafficserver.readthedocs.org/en/latest/reference/configuration/records.config.en.html
> The value of proxy.config.http.cache.ignore_accept_mismatch has no bearing on
> this issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
