You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@trafficserver.apache.org by "Leif Hedstrom (JIRA)" <ji...@apache.org> on 2014/09/16 23:04:34 UTC

[jira] [Resolved] (TS-3077) log cache hit or miss codes

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

Leif Hedstrom resolved TS-3077.
-------------------------------
    Resolution: Duplicate

I'm going to merge this with TS-3036, I have a patch which incorporates TS-3036 into the requirements for this feature.

> log cache hit or miss codes
> ---------------------------
>
>                 Key: TS-3077
>                 URL: https://issues.apache.org/jira/browse/TS-3077
>             Project: Traffic Server
>          Issue Type: Bug
>            Reporter: Miles Libbey
>            Assignee: Leif Hedstrom
>             Fix For: 5.2.0
>
>
> We are currently using the log item crc "The cache result code; specifies how the cache responded to the request (HIT, MISS, and so on)."  however, when there is an error (like the client aborts), the crc field becomes
> ERR_CLIENT_ABORT
> ERR_CONNECT_FAIL
> ERR_READ_TIMEOUT
> etc.  ERR_CLIENT_ABORT	and	ERR_CONNECT_FAIL don't seem to be really cache Status related.  WOuld still be nice to know if the error happened on a hit or miss.



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