TCP_REFRESH_HIT/206
14566 TCP_REFRESH_HIT/304
I understand the REFRESH cases, but what about the first three? Under
what circumstances does a (non-REFRESH) cache hit none-the-less cause a
fetch to an origin server?
Thanks,
ht
--
Henry S. Thompson, School of Informatics, University of Edinburgh
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 ==
&
conds_"? My understanding was that
kernel time differences were typically accurate to ~100 _nanoseconds_.
If you can easily tell me where to look in the source, obviously that's
what I should do
ht
--
Henry S. Thompson, School of Informatics, University of Edinburgh
1
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 ==
&
negative.
> Note that its on the scale of ~100 milliseconds.
Sorry but I still don't see how two successive fetchs could result in a
decrement (w/o an NTP intervention).
The negative numbers I'm seeing range up into the low 1000s (of msec,
right? That's what the squid documentation says, IIRC).
Di
?
Sorry for these queries of mostly historical interest for most people,
but I've looked fairly hard for earlier discussion of these oddities w/o
success.
Thanks,
ht
--
Henry S. Thompson, School of Informatics, University of Edinburgh
10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND
Amos Jeffries writes:
> On 25/07/2016 10:34 p.m., Henry S. Thompson wrote:
>> Standard squid config only logs one CONNECT line for any https
>> transaction. What is being counted/timed by the reported bytes and
>> duration fields in that line?
>>
>> I'm g
connection
established by that CONNECT, but I can't find anything in the log
documentation which confirms that.
Thanks,
ht
--
Henry S. Thompson, School of Informatics, University of Edinburgh
10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440
Fax: (44
Leonardo Rodrigues writes:
Em 24/06/15 15:28, Henry S. Thompson escreveu:
I've searched the documentation and mailing list archives w/o success,
and am not competent to read the source, so asking here: what is
logged as the 'remotehost' in Squid logs when a request that has been
encapsulated
Antony Stone writes:
On Friday 26 Jun 2015 at 09:51, Henry S. Thompson wrote:
logs will show the IP address that reached squid, ie. the source
address of the connection. If that was NATted, squid will never know
(and thus is not able to log) the original address before the NAT
, or from a machine accessing the proxy via a VPN
connection?
Thanks,
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: h...@inf.ed.ac.uk
11 matches
Mail list logo