[
https://issues.apache.org/jira/browse/TS-3055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14515863#comment-14515863
]
Leif Hedstrom commented on TS-3055:
-----------------------------------
I've seen some oddities here whereas arbitrarily, 203, 300 and 410 responses
are cached per heuristics, since there's no explicit CC: header. But for the
same setup, e.g. 403 / 404 are not being cached.
So we're definitely not consistent here (albeit, we're doing things correct as
far as I can tell).
> Update cacheability behavior as per new BIS RFC
> -----------------------------------------------
>
> Key: TS-3055
> URL: https://issues.apache.org/jira/browse/TS-3055
> Project: Traffic Server
> Issue Type: Bug
> Components: HTTP
> Reporter: Leif Hedstrom
> Fix For: 6.0.0
>
>
> We should make sure that our implementation follows the (updated) RFC,
> http://tools.ietf.org/html/rfc7231#section-6.1 as far as cacheability goes
> for various status codes. Also, we should examine how this interacts with our
> negative caching option, maybe that option should be eliminated now that
> things are much clearer.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
