Amos Jeffries writes:
> On 5/08/2016 12:37 a.m., Henry S. Thompson wrote:
>> Thanks for your patience with this, but still not quite getting it.
>>
>> I thought there were two cases:
>>
>> 1) Client drops the connection before the interaction is complete ==
>> log shows HTTP result code 000, almost always size 0 as well;
>>
>> 2) Interaction completed successfully == HTTP result code as from
>> cache or remote, size as sent to client.
>>
>> See below how I can't make that fit with your reply
>
> #1 is correct but incomplete. The 000 status means dropped any time
> before the status to be delivered became known. So while "incomplete" is
> true, there are very short times in the transaction where "incomplete"
> is still true but are logged with non-000 status and size 0.
Right, that's helpful, thanks.
> NP: There are also later times during payload delivery where drop can
> happen so incomplete is still true and both status and size have values.
> Those are impossible to detect in HTTP/1.0, so another reason to upgrade
> to HTTP/1.1 software (Squid-3.2+).
Understood.
> The difference in timing between all these state changes should be a
> very, very small number of milliseconds. Enough to see differently in
> logs sometimes but should not be something to worry about.
Right.
ht
--
Henry S. Thompson, School of Informatics, University of Edinburgh
10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440
Fax: (44) 131 650-4587, e-mail: ht@xxxxxxxxxxxx
URL: http://www.ltg.ed.ac.uk/~ht/
[mail from me _always_ has a .sig like this -- mail without it is forged spam]
_______________________________________________
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
http://lists.squid-cache.org/listinfo/squid-users
