[
https://issues.apache.org/jira/browse/TS-3055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14517577#comment-14517577
]
Leif Hedstrom commented on TS-3055:
-----------------------------------
So, examined a little more, and the code behaves as expected, albeit rather
inconsistent with current RFCs:
{code}
if ((response_code == HTTP_STATUS_OK) || (response_code ==
HTTP_STATUS_NOT_MODIFIED) ||
(response_code == HTTP_STATUS_NON_AUTHORITATIVE_INFORMATION) ||
(response_code == HTTP_STATUS_MOVED_PERMANENTLY) ||
(response_code == HTTP_STATUS_MULTIPLE_CHOICES) || (response_code ==
HTTP_STATUS_GONE)) {
DebugTxn("http_trans", "[is_response_cacheable] YES by default ");
return true;
{code}
> 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)
