You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Bryan Call (JIRA)" <ji...@apache.org> on 2016/08/16 15:24:20 UTC

[jira] [Updated] (TS-2204) ts should treat unrecognized codes as the base code (2xx, 3xx, 4xx, etc)

     [ https://issues.apache.org/jira/browse/TS-2204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bryan Call updated TS-2204:
---------------------------
    Summary: ts should treat unrecognized codes as the base code (2xx, 3xx, 4xx, etc)  (was: ts should not cache the response with unrecognized codes)

> ts should treat unrecognized codes as the base code (2xx, 3xx, 4xx, etc)
> ------------------------------------------------------------------------
>
>                 Key: TS-2204
>                 URL: https://issues.apache.org/jira/browse/TS-2204
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: Cache, HTTP
>            Reporter: Zhao Yongming
>             Fix For: sometime
>
>
> according to RFC 2616:  6.1.1
>    HTTP status codes are extensible. HTTP applications are not required
>    to understand the meaning of all registered status codes, though such
>    understanding is obviously desirable. However, applications MUST
>    understand the class of any status code, as indicated by the first
>    digit, and treat any unrecognized response as being equivalent to the
>    x00 status code of that class, with the exception that an
>    unrecognized response MUST NOT be cached. For example, if an
>    unrecognized status code of 431 is received by the client, it can
>    safely assume that there was something wrong with its request and
>    treat the response as if it had received a 400 status code. In such
>    cases, user agents SHOULD present to the user the entity returned
>    with the response, since that entity is likely to include human-
>    readable information which will explain the unusual status.
> and we should not cache any of the unknown response.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)