Hello,
What may help us move forward is a "reverse mapping" table like this
one:
Row (client-Squid) headings:
* response body sent by Squid to client
* 304 response sent by Squid to client
* 412 response sent by Squid to client
...
Column (Squid-server) headings:
* no contact with the serve
On 15/10/2016 1:36 a.m., Yuri Voinov wrote:
>
>
>
> 14.10.2016 18:30, Amos Jeffries пишет:
>> On 15/10/2016 12:34 a.m., Yuri Voinov wrote:
>>>
>>> A bit more details.
>>>
>>> This is 4 transactions in chronological order. Two from wget -S and two
>>> from same PC via browser for the same URL:
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Well. Let's made clean, easy to reproduce example.
Let's take one PC behind proxy. Let's clean up any browser's caches.
Let's reboot it for experiment clarity.
Let's take two URLs. One for HTTP and the same for HTTPS. Simple static
image 200 Kb i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
14.10.2016 18:30, Amos Jeffries пишет:
> On 15/10/2016 12:34 a.m., Yuri Voinov wrote:
>>
>> A bit more details.
>>
>> This is 4 transactions in chronological order. Two from wget -S and two
>> from same PC via browser for the same URL:
>>
>> *roo
On 15/10/2016 12:34 a.m., Yuri Voinov wrote:
>
> A bit more details.
>
> This is 4 transactions in chronological order. Two from wget -S and two
> from same PC via browser for the same URL:
>
> *root @ khorne /tmp # wget -S
> http://www.gazeta.ru/nm2015/js/gazeta.media.query.js*
> --2016-10-14 1
On 14/10/2016 10:44 a.m., Yuri Voinov wrote:
>
>
>
> 14.10.2016 2:48, Alex Rousskov пишет:
>> On 10/13/2016 01:44 PM, Yuri Voinov wrote:
>
>>> However, this is nothing more than word games, Alex.
>
>> ... unless the definition of a hit affects your billing or your
>> interpretation of Squid do
On 14/10/2016 10:57 p.m., Yuri Voinov wrote:
>
> It seems I found the root of problem.
>
> When cached object refreshed and goes via HTTP, it gives
> TCP_REFRESH_UNMODIFIED in access.log, which is correct.
> When the _same_ _cached_ _object_ refreshes and goes via HTTPS, it gives
> TCP_MISS/304 i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
A bit more details.
This is 4 transactions in chronological order. Two from wget -S and two
from same PC via browser for the same URL:
*root @ khorne /tmp # wget -S
http://www.gazeta.ru/nm2015/js/gazeta.media.query.js*
- --2016-10-14 17:18:05--
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
It seems I found the root of problem.
When cached object refreshed and goes via HTTP, it gives
TCP_REFRESH_UNMODIFIED in access.log, which is correct.
When the _same_ _cached_ _object_ refreshes and goes via HTTPS, it gives
TCP_MISS/304 in access.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
14.10.2016 2:48, Alex Rousskov пишет:
> On 10/13/2016 01:44 PM, Yuri Voinov wrote:
>
>> However, this is nothing more than word games, Alex.
>
> ... unless the definition of a hit affects your billing or your
> interpretation of Squid documentati
On 10/13/2016 01:44 PM, Yuri Voinov wrote:
> However, this is nothing more than word games, Alex.
... unless the definition of a hit affects your billing or your
interpretation of Squid documentation or the developer interpretation of
the code. Definitions matter! You yourself have seen their im
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
14.10.2016 1:28, Alex Rousskov пишет:
> On 10/13/2016 12:46 PM, Yuri Voinov wrote:
>>
>>
>> 14.10.2016 0:28, Alex Rousskov пишет:
>>> On 10/13/2016 11:52 AM, Yuri Voinov wrote:
When we seen ??/304 with only headers - most probably conten
On 10/13/2016 12:46 PM, Yuri Voinov wrote:
>
>
> 14.10.2016 0:28, Alex Rousskov пишет:
>> On 10/13/2016 11:52 AM, Yuri Voinov wrote:
>>> When we seen ??/304 with only headers - most probably content behind
>>> proxy already and this is CLIENT_IMS_HIT observed.
>> A 304 code sent by Squid to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
14.10.2016 0:28, Alex Rousskov пишет:
> On 10/13/2016 11:52 AM, Yuri Voinov wrote:
>> When we seen ??/304 with only headers - most probably content behind
>> proxy already and this is CLIENT_IMS_HIT observed.
>>
>> Yes, of course, we don't kno
On 10/13/2016 11:52 AM, Yuri Voinov wrote:
> When we seen ??/304 with only headers - most probably content behind
> proxy already and this is CLIENT_IMS_HIT observed.
>
> Yes, of course, we don't know is this content really in client cache.
> But this is don't care - proxy shared cache contain
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
13.10.2016 21:02, Yuri Voinov пишет:
>
>
>
> 13.10.2016 20:09, Amos Jeffries пишет:
> > On 14/10/2016 2:46 a.m., Yuri Voinov wrote:
> >>
> >>
> >>
> >> 13.10.2016 19:44, Yuri Voinov пишет:
> >>
> >>
> >>
> >>> 13.10.2016 19:41, Amos Jeffries пише
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I do not pretend that I have seen everything.
But my personal statistics across multiple servers over they access.log
shows that TCP_MISS/304 in all cases associated with the update
downloaded content (reload/refresh). Accordingly, the logging of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
13.10.2016 20:09, Amos Jeffries пишет:
> On 14/10/2016 2:46 a.m., Yuri Voinov wrote:
>>
>>
>>
>> 13.10.2016 19:44, Yuri Voinov пишет:
>>
>>
>>
>>> 13.10.2016 19:41, Amos Jeffries пишет:
On 14/10/2016 1:38 a.m., Yuri Voinov wrote:
>
>
On 14/10/2016 2:46 a.m., Yuri Voinov wrote:
>
>
>
> 13.10.2016 19:44, Yuri Voinov пишет:
>
>
>
>> 13.10.2016 19:41, Amos Jeffries пишет:
>>> On 14/10/2016 1:38 a.m., Yuri Voinov wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi gents.
I have very stu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
13.10.2016 19:44, Yuri Voinov пишет:
>
>
>
> 13.10.2016 19:41, Amos Jeffries пишет:
> > On 14/10/2016 1:38 a.m., Yuri Voinov wrote:
> >>
> >> -BEGIN PGP SIGNED MESSAGE-
> >> Hash: SHA256
> >>
> >> Hi gents.
> >>
> >> I have very stupid qu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
13.10.2016 19:41, Amos Jeffries пишет:
> On 14/10/2016 1:38 a.m., Yuri Voinov wrote:
>>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA256
>>
>> Hi gents.
>>
>> I have very stupid question.
>>
>> Look at this access.log entry:
>>
>> 147623601
On 14/10/2016 1:38 a.m., Yuri Voinov wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Hi gents.
>
> I have very stupid question.
>
> Look at this access.log entry:
>
> 1476236018.506 85 192.168.100.103 TCP_MISS/304 354 GET
> https://www.gazeta.ru/nm2015/gzt/img/logo_footer
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi gents.
I have very stupid question.
Look at this access.log entry:
1476236018.506 85 192.168.100.103 TCP_MISS/304 354 GET
https://www.gazeta.ru/nm2015/gzt/img/logo_footer.png -
HIER_DIRECT/81.19.72.2 -
I'm see this:
http://wiki.squid-ca
23 matches
Mail list logo