[
https://issues.apache.org/jira/browse/TS-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Miles Libbey reopened TS-2109:
------------------------------
If this was fixed in 5, its back to broken. no-cache differs from no-store in
that the proxy can cache the response, but must validate the object every time
(like with an IMS request).
A few code snippets:
if (!s->cache_info.directives.does_server_permit_storing &&
!s->cache_control.ignore_server_no_cache &&
(s->cache_control.ttl_in_cache <= 0)) {
DebugTxn("http_trans", "[is_response_cacheable] server does not permit
storing and config file does not "
"indicate that server directive should be ignored");
return false;
}
...
bool
HttpTransactHeaders::does_server_allow_response_to_be_stored(HTTPHdr *resp)
{
uint32_t cc_mask = (MIME_COOKED_MASK_CC_NO_CACHE |
MIME_COOKED_MASK_CC_NO_STORE | MIME_COOKED_MASK_CC_PRIVATE);
if ((resp->get_cooked_cc_mask() & cc_mask) ||
(resp->get_cooked_pragma_no_cache())) {
return false;
} else {
return true;
}
}
so, CC: no-cache *or* CC: no-store *or* CC: private would all not be
cacheable.
> Cache-Control: no-cache responses are not stored the cache
> ----------------------------------------------------------
>
> Key: TS-2109
> URL: https://issues.apache.org/jira/browse/TS-2109
> Project: Traffic Server
> Issue Type: Bug
> Components: Cache
> Reporter: Igor Brezac
>
> This can be duplicated using 3.3.5-dev (trunk).
> Cache-Control: must-revalidate suffers from the same issue.
> Cache-Control: max-age=0,must-revalidate works correctly
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)