[
https://issues.apache.org/jira/browse/TS-2633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13935213#comment-13935213
]
Sudheer Vinukonda commented on TS-2633:
---------------------------------------
The issue appears to be due to the below piece of code in HttpTransact.cc. With
Bryan's help, will try to submit a patch soon.
void
HttpTransact::handle_cache_operation_on_forward_server_response(State* s)
{
//...........
...........
s->negative_caching = is_negative_caching_appropriate(s);
//..........
//.....
} else if (s->cache_info.action == CACHE_DO_WRITE) {
if (!cacheable && !s->negative_caching) {
s->cache_info.action = CACHE_DO_NO_ACTION;
} else if (s->method == HTTP_WKSIDX_HEAD) {
///....................
> 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: Bryan Call
> Fix For: 5.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.2#6252)
