Re: 000 response codes

On Tue, 28 Mar 2000, Dancer wrote:

> Only half a dev question, though this may involve me hacking some
> source...
>
> Hrm. I've been thrown a question from our support people about squid
> response codes. Specifically 000.
>
> Now _my_ interpretation is that it means: No valid HTTP response code
> (ie: Connection failed, or was aborted before any data happened, or has
> to do with UDP).
>
> However, we have a selection of:
> TCP_REFRESH_HIT/000
> TCP_MISS/000
> TCP_HIT/000
>
> Some have delivered bytes next to them. A few are marked with 0 bytes
> (I
> presume the user pressed stop).
>
> So, two questions. What can generate this? And should we break some of
> these cases out into subcodes (001,002,099)?

As you guessed, these probably come from aborted requests.
Another possibility is that the HTTP response was malformed, and
didn't have a status code.

After looking at my own cache logs, I also see a lot of 000's that
I can't explain.

Duane W.
Received on Thu Mar 30 2000 - 11:13:20 MST