squid-avira-update-cache

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
10 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

squid-avira-update-cache

splicelid
Hi all, I'm trying to cache "avira updates" with squid, but no luck...

my conf:
acl aviraupdate dstdomain .avira-update.com
range_offset_limit -1 aviraupdate
refresh_pattern -i avira-update.com/.*\.* 4320 80% 43200 reload-into-ims

any help ? 10x!

_______________________________________________
squid-users mailing list
[hidden email]
http://lists.squid-cache.org/listinfo/squid-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: squid-avira-update-cache

Yuri Voinov

Any logs?


17.02.2017 17:43, [hidden email] пишет:
Hi all, I'm trying to cache "avira updates" with squid, but no luck...

my conf:
acl aviraupdate dstdomain .avira-update.com
range_offset_limit -1 aviraupdate
refresh_pattern -i avira-update.com/.*\.* 4320 80% 43200 reload-into-ims

any help ? 10x!


_______________________________________________
squid-users mailing list
[hidden email]
http://lists.squid-cache.org/listinfo/squid-users

--
Bugs to the Future

_______________________________________________
squid-users mailing list
[hidden email]
http://lists.squid-cache.org/listinfo/squid-users

0x613DEC46.asc (2K) Download Attachment
signature.asc (484 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: squid-avira-update-cache

Yuri Voinov
In reply to this post by splicelid

root @ khorne /patch # wget -S http://personal.avira-update.com/update/x_vdf_sigver/7.12.155.64_8.12.155.64/xbv00050.vdf.lz
--2017-02-17 23:51:22--  http://personal.avira-update.com/update/x_vdf_sigver/7.12.155.64_8.12.155.64/xbv00050.vdf.lz
Connecting to 127.0.0.1:3128... connected.
Proxy request sent, awaiting response...
  HTTP/1.1 200 OK
  Server: Apache
  ETag: "934c1d64b13126c7daada1daf0fe3845:1487280555"
  Last-Modified: Thu, 16 Feb 2017 21:26:06 GMT
  Accept-Ranges: bytes
  Content-Length: 2023
  Content-Type: text/plain
  Cache-Control: max-age=45
  Expires: Fri, 17 Feb 2017 17:52:13 GMT
  Date: Fri, 17 Feb 2017 17:51:28 GMT
  X-Cache: MISS from khorne
  X-Cache-Lookup: MISS from khorne:3128
  Connection: keep-alive
Length: 2023 (2.0K) [text/plain]
Saving to: 'xbv00050.vdf.lz'

xbv00050.vdf.lz     100%[===================>]   1.98K  --.-KB/s    in 0s     

2017-02-17 23:51:28 (176 MB/s) - 'xbv00050.vdf.lz' saved [2023/2023]

root @ khorne /patch # wget -S http://personal.avira-update.com/update/x_vdf_sigver/7.12.155.64_8.12.155.64/xbv00050.vdf.lz
--2017-02-17 23:51:40--  http://personal.avira-update.com/update/x_vdf_sigver/7.12.155.64_8.12.155.64/xbv00050.vdf.lz
Connecting to 127.0.0.1:3128... connected.
Proxy request sent, awaiting response...
  HTTP/1.1 200 OK
  Server: Apache
  ETag: "934c1d64b13126c7daada1daf0fe3845:1487280555"
  Last-Modified: Thu, 16 Feb 2017 21:26:06 GMT
  Accept-Ranges: bytes
  Content-Length: 2023
  Content-Type: text/plain
  Cache-Control: max-age=45
  X-Origin-Date: Fri, 17 Feb 2017 17:51:28 GMT
  Date: Fri, 17 Feb 2017 17:51:40 GMT
  X-Origin-Expires: Fri, 17 Feb 2017 17:52:13 GMT
  Expires: Fri, 17 Feb 2017 17:52:25 GMT
  X-Cache-Age: 12
  X-Cache: HIT from khorne
  X-Cache-Lookup: HIT from khorne:3128
  Connection: keep-alive
Length: 2023 (2.0K) [text/plain]
Saving to: 'xbv00050.vdf.lz.1'

xbv00050.vdf.lz.1   100%[===================>]   1.98K  --.-KB/s    in 0s     

2017-02-17 23:51:40 (233 MB/s) - 'xbv00050.vdf.lz.1' saved [2023/2023]

root @ khorne /patch # wget -S http://personal.avira-update.com/update/x_vdf_sigver/7.12.155.64_8.12.155.64/xbv00044.vdf.lz
--2017-02-17 23:52:22--  http://personal.avira-update.com/update/x_vdf_sigver/7.12.155.64_8.12.155.64/xbv00044.vdf.lz
Connecting to 127.0.0.1:3128... connected.
Proxy request sent, awaiting response...
  HTTP/1.1 200 OK
  Server: Apache
  ETag: "953d632488104f11aa7252533ce6389b:1487280555"
  Last-Modified: Thu, 16 Feb 2017 21:26:06 GMT
  Accept-Ranges: bytes
  Content-Length: 13443
  Content-Type: text/plain
  Cache-Control: max-age=162
  Expires: Fri, 17 Feb 2017 17:55:04 GMT
  Date: Fri, 17 Feb 2017 17:52:22 GMT
  X-Cache: MISS from khorne
  X-Cache-Lookup: MISS from khorne:3128
  Connection: keep-alive
Length: 13443 (13K) [text/plain]
Saving to: 'xbv00044.vdf.lz'

xbv00044.vdf.lz     100%[===================>]  13.13K  --.-KB/s    in 0.003s 

2017-02-17 23:52:22 (4.20 MB/s) - 'xbv00044.vdf.lz' saved [13443/13443]

root @ khorne /patch # wget -S http://personal.avira-update.com/update/x_vdf_sigver/7.12.155.64_8.12.155.64/xbv00044.vdf.lz
--2017-02-17 23:52:23--  http://personal.avira-update.com/update/x_vdf_sigver/7.12.155.64_8.12.155.64/xbv00044.vdf.lz
Connecting to 127.0.0.1:3128... connected.
Proxy request sent, awaiting response...
  HTTP/1.1 200 OK
  Server: Apache
  ETag: "953d632488104f11aa7252533ce6389b:1487280555"
  Last-Modified: Thu, 16 Feb 2017 21:26:06 GMT
  Accept-Ranges: bytes
  Content-Length: 13443
  Content-Type: text/plain
  Cache-Control: max-age=162
  X-Origin-Date: Fri, 17 Feb 2017 17:52:22 GMT
  Date: Fri, 17 Feb 2017 17:52:23 GMT
  X-Origin-Expires: Fri, 17 Feb 2017 17:55:04 GMT
  Expires: Fri, 17 Feb 2017 17:55:05 GMT
  X-Cache-Age: 1
  X-Cache: HIT from khorne
  X-Cache-Lookup: HIT from khorne:3128
  Connection: keep-alive
Length: 13443 (13K) [text/plain]
Saving to: 'xbv00044.vdf.lz.1'

xbv00044.vdf.lz.1   100%[===================>]  13.13K  --.-KB/s    in 0.03s  

2017-02-17 23:52:23 (441 KB/s) - 'xbv00044.vdf.lz.1' saved [13443/13443]

Well, let's give big Avira file:


root @ khorne /patch # wget -S http://personal.avira-update.com/update/n_vdf/vbase005.vdf.gz
--2017-02-17 23:54:04--  http://personal.avira-update.com/update/n_vdf/vbase005.vdf.gz
Connecting to 127.0.0.1:3128... connected.
Proxy request sent, awaiting response...
  HTTP/1.1 200 OK
  Server: Apache
  ETag: "5af09f9e8a3d09809ce8005ddb55fa7d:1487352426"
  Last-Modified: Fri, 17 Feb 2017 17:25:36 GMT
  Accept-Ranges: bytes
  Content-Length: 11556885
  Content-Type: application/x-gzip
  Cache-Control: max-age=185
  Expires: Fri, 17 Feb 2017 17:57:09 GMT
  Date: Fri, 17 Feb 2017 17:54:04 GMT
  X-Cache: MISS from khorne
  X-Cache-Lookup: MISS from khorne:3128
  Connection: keep-alive
Length: 11556885 (11M) [application/x-gzip]
Saving to: 'vbase005.vdf.gz'

vbase005.vdf.gz     100%[===================>]  11.02M   471KB/s    in 24s    

2017-02-17 23:54:28 (471 KB/s) - 'vbase005.vdf.gz' saved [11556885/11556885]

root @ khorne /patch # wget -S http://personal.avira-update.com/update/n_vdf/vbase005.vdf.gz
--2017-02-17 23:54:29--  http://personal.avira-update.com/update/n_vdf/vbase005.vdf.gz
Connecting to 127.0.0.1:3128... connected.
Proxy request sent, awaiting response...
  HTTP/1.1 200 OK
  Server: Apache
  ETag: "5af09f9e8a3d09809ce8005ddb55fa7d:1487352426"
  Last-Modified: Fri, 17 Feb 2017 17:25:36 GMT
  Accept-Ranges: bytes
  Content-Length: 11556885
  Content-Type: application/x-gzip
  Cache-Control: max-age=185
  X-Origin-Date: Fri, 17 Feb 2017 17:54:04 GMT
  Date: Fri, 17 Feb 2017 17:54:29 GMT
  X-Origin-Expires: Fri, 17 Feb 2017 17:57:09 GMT
  Expires: Fri, 17 Feb 2017 17:57:34 GMT
  X-Cache-Age: 25
  X-Cache: HIT from khorne
  X-Cache-Lookup: HIT from khorne:3128
  Connection: keep-alive
Length: 11556885 (11M) [application/x-gzip]
Saving to: 'vbase005.vdf.gz.1'

vbase005.vdf.gz.1   100%[===================>]  11.02M   1545KB/s    in 4s    

2017-02-17 23:54:53 (468 KB/s) - 'vbase005.vdf.gz.1' saved [11556885/11556885]

See no problem to cache this. Check your config. May be you have some stuff in squid.conf which preventing caching.

17.02.2017 17:43, [hidden email] пишет:
Hi all, I'm trying to cache "avira updates" with squid, but no luck...

my conf:
acl aviraupdate dstdomain .avira-update.com
range_offset_limit -1 aviraupdate
refresh_pattern -i avira-update.com/.*\.* 4320 80% 43200 reload-into-ims

any help ? 10x!


_______________________________________________
squid-users mailing list
[hidden email]
http://lists.squid-cache.org/listinfo/squid-users

--
Bugs to the Future

_______________________________________________
squid-users mailing list
[hidden email]
http://lists.squid-cache.org/listinfo/squid-users

0x613DEC46.asc (2K) Download Attachment
signature.asc (484 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: squid-avira-update-cache

Heiler Bemerguy
In reply to this post by Yuri Voinov


I've noticed this:

2017/02/17 16:28:05.632 kid4| ctx: enter level  0: 'http://personal.avira-update.com/update/idx/localdecider_sigver-win32-int-13.0.1.12.info.lz'
2017/02/17 16:28:05.632 kid4| 22,3| http.cc(339) cacheableReply: NO because e:=p2XDIV/0x15c49190*3 has been released.
2017/02/17 16:28:05.797 kid4| ctx: enter level  0: 'http://personal.avira-update.com/update/idx/weblocaldecider_sigver-win32-int-15.0.15.28.info.lz'
2017/02/17 16:28:05.797 kid4| 22,3| http.cc(339) cacheableReply: NO because e:=p2XDIV/0x15c49190*3 has been released.
2017/02/17 16:28:17.803 kid4| ctx: enter level  0: 'http://personal.avira-update.com/update/x_vdf_sigver/7.12.155.132_8.12.155.132/aevdf.dat.lz'
2017/02/17 16:28:17.803 kid4| 22,3| http.cc(339) cacheableReply: NO because e:=p2XDIV/0x6a233d0*3 has been released.

It seems I'm not caching it too, but couldn't understand what "has been released" is referring too.

Squid Cache: Version 4.0.18


-- 
Best Regards,

Heiler Bemerguy
Network Manager - CINBESA
55 91 98151-4894/3184-1751

Em 17/02/2017 11:52, Yuri Voinov escreveu:

Any logs?


17.02.2017 17:43, [hidden email] пишет:
Hi all, I'm trying to cache "avira updates" with squid, but no luck...

my conf:
acl aviraupdate dstdomain .avira-update.com
range_offset_limit -1 aviraupdate
refresh_pattern -i avira-update.com/.*\.* 4320 80% 43200 reload-into-ims

any help ? 10x!


_______________________________________________
squid-users mailing list
[hidden email]
http://lists.squid-cache.org/listinfo/squid-users

--
Bugs to the Future


_______________________________________________
squid-users mailing list
[hidden email]
http://lists.squid-cache.org/listinfo/squid-users


_______________________________________________
squid-users mailing list
[hidden email]
http://lists.squid-cache.org/listinfo/squid-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: squid-avira-update-cache

Alex Rousskov
On 02/17/2017 12:31 PM, Heiler Bemerguy wrote:

>
> I've noticed this:
>
> 2017/02/17 16:28:05.632 kid4| ctx: enter level  0:
> 'http://personal.avira-update.com/update/idx/localdecider_sigver-win32-int-13.0.1.12.info.lz'
> 2017/02/17 16:28:05.632 kid4| 22,3| http.cc(339) cacheableReply: NO
> because e:=p2XDIV/0x15c49190*3 has been released.
> 2017/02/17 16:28:05.797 kid4| ctx: enter level  0:
> 'http://personal.avira-update.com/update/idx/weblocaldecider_sigver-win32-int-15.0.15.28.info.lz'
> 2017/02/17 16:28:05.797 kid4| 22,3| http.cc(339) cacheableReply: NO
> because e:=p2XDIV/0x15c49190*3 has been released.
> 2017/02/17 16:28:17.803 kid4| ctx: enter level  0:
> 'http://personal.avira-update.com/update/x_vdf_sigver/7.12.155.132_8.12.155.132/aevdf.dat.lz'
> 2017/02/17 16:28:17.803 kid4| 22,3| http.cc(339) cacheableReply: NO
> because e:=p2XDIV/0x6a233d0*3 has been released.
>
> It seems I'm not caching it too, but couldn't understand what "has been
> released" is referring too.

In this debugging context, "has been released" means that the response
was marked for removal from the cache some time earlier. It will be
delivered to the current client (or several concurrent clients in some
cases) but it will not be available to future clients.

These debugging lines do not tell us why or when that marking was
applied. It is possible that the response had some anti-caching
Cache-Control headers or was too big to cache, but these are just two
examples; there are lots of other possible reasons.


HTH,

Alex.

_______________________________________________
squid-users mailing list
[hidden email]
http://lists.squid-cache.org/listinfo/squid-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: squid-avira-update-cache

Heiler Bemerguy



Em 17/02/2017 17:05, Alex Rousskov escreveu:
On 02/17/2017 12:31 PM, Heiler Bemerguy wrote:
I've noticed this:

2017/02/17 16:28:05.632 kid4| ctx: enter level  0:
'http://personal.avira-update.com/update/idx/localdecider_sigver-win32-int-13.0.1.12.info.lz'
2017/02/17 16:28:05.632 kid4| 22,3| http.cc(339) cacheableReply: NO
because e:=p2XDIV/0x15c49190*3 has been released.
2017/02/17 16:28:05.797 kid4| ctx: enter level  0:
'http://personal.avira-update.com/update/idx/weblocaldecider_sigver-win32-int-15.0.15.28.info.lz'
2017/02/17 16:28:05.797 kid4| 22,3| http.cc(339) cacheableReply: NO
because e:=p2XDIV/0x15c49190*3 has been released.
2017/02/17 16:28:17.803 kid4| ctx: enter level  0:
'http://personal.avira-update.com/update/x_vdf_sigver/7.12.155.132_8.12.155.132/aevdf.dat.lz'
2017/02/17 16:28:17.803 kid4| 22,3| http.cc(339) cacheableReply: NO
because e:=p2XDIV/0x6a233d0*3 has been released.

It seems I'm not caching it too, but couldn't understand what "has been
released" is referring too.
In this debugging context, "has been released" means that the response
was marked for removal from the cache some time earlier. It will be
delivered to the current client (or several concurrent clients in some
cases) but it will not be available to future clients.

These debugging lines do not tell us why or when that marking was
applied. It is possible that the response had some anti-caching
Cache-Control headers or was too big to cache, but these are just two
examples; there are lots of other possible reasons.

When you say "some time earlier", you mean days? Because today, every mention to "avira-update" just shows up those lines.. here's a bigger log:

2017/02/17 17:17:46.328 kid2| ctx: enter level  0: 'http://img.olx.com.br/thumbsli/87/873721001890097.jpg'
2017/02/17 17:17:46.328 kid2| 22,3| refresh.cc(280) refreshCheck: checking freshness of URI: http://img.olx.com.br/thumbsli/87/873721001890097.jpg
2017/02/17 17:17:46.328 kid2| 22,3| refresh.cc(302) refreshCheck: Matched '\.(jp[eg]{1,2}|pdf|gif|pn[pg]|bmp|tiff|ico|swf|css|js|ad|png)\??$ 604800 80%% 7257600'
2017/02/17 17:17:46.328 kid2| 22,3| refresh.cc(304) refreshCheck:       age:    60
2017/02/17 17:17:46.328 kid2| 22,3| refresh.cc(306) refreshCheck:       check_time:     Fri, 17 Feb 2017 20:18:46 GMT
2017/02/17 17:17:46.328 kid2| 22,3| refresh.cc(308) refreshCheck:       entry->timestamp:       Fri, 17 Feb 2017 20:17:46 GMT
2017/02/17 17:17:46.328 kid2| 22,3| refresh.cc(156) refreshStaleness: FRESH: expires 1487962999 >= check_time 1487362726
2017/02/17 17:17:46.328 kid2| 22,3| refresh.cc(328) refreshCheck: Staleness = -1
2017/02/17 17:17:46.328 kid2| 22,3| refresh.cc(453) refreshCheck: Object isn't stale..
2017/02/17 17:17:46.328 kid2| 22,3| refresh.cc(455) refreshCheck: returning FRESH_EXPIRES
2017/02/17 17:17:46.328 kid2| 22,3| http.cc(488) cacheableReply: YES because HTTP status 200
2017/02/17 17:17:46.431 kid2| ctx: exit level  0
2017/02/17 17:17:46.432 kid2| ctx: enter level  0: 'http://personal.avira-update.com/update/idx/webcat_sigver-common-int-2017_9.0.217.1900.info.lz'
2017/02/17 17:17:46.432 kid2| 22,3| http.cc(339) cacheableReply: NO because e:=p2XDIV/0x1fcb650*3 has been released.
2017/02/17 17:17:46.600 kid2| ctx: exit level  0
2017/02/17 17:17:46.600 kid2| ctx: enter level  0: 'http://personal.avira-update.com/update/idx/localdecider_sigver-win32-int-13.0.1.12.info.lz'
2017/02/17 17:17:46.600 kid2| 22,3| http.cc(339) cacheableReply: NO because e:=p2XDIV/0x1fcb650*3 has been released.
2017/02/17 17:17:46.732 kid2| ctx: exit level  0
2017/02/17 17:17:46.732 kid2| 22,3| refresh.cc(646) getMaxAge: getMaxAge: 'http://img.olx.com.br/thumbsli/14/142717018210327.jpg'
2017/02/17 17:17:46.769 kid2| ctx: enter level  0: 'http://personal.avira-update.com/update/idx/weblocaldecider_sigver-win32-int-15.0.15.28.info.lz'
2017/02/17 17:17:46.769 kid2| 22,3| http.cc(339) cacheableReply: NO because e:=p2XDIV/0x1fcb650*3 has been released.
2017/02/17 17:17:46.791 kid2| ctx: exit level  0
2017/02/17 17:17:46.791 kid2| 22,3| refresh.cc(280) refreshCheck: checking freshness of URI: http://www.googletagservices.com/tag/js/gpt.js

I was using ALL,3 and cat cache.log |grep -C 10 avira-update |grep kid2

--
Best Regards,

Heiler Bemerguy
Network Manager - CINBESA
55 91 98151-4894/3184-1751

_______________________________________________
squid-users mailing list
[hidden email]
http://lists.squid-cache.org/listinfo/squid-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: squid-avira-update-cache

Alex Rousskov
On 02/17/2017 01:27 PM, Heiler Bemerguy wrote:

> Em 17/02/2017 17:05, Alex Rousskov escreveu:
>> On 02/17/2017 12:31 PM, Heiler Bemerguy wrote:
>>> I've noticed this:
>>>
>>> 2017/02/17 16:28:05.632 kid4| ctx: enter level  0:
>>> 'http://personal.avira-update.com/update/idx/localdecider_sigver-win32-int-13.0.1.12.info.lz'
>>> 2017/02/17 16:28:05.632 kid4| 22,3| http.cc(339) cacheableReply: NO
>>> because e:=p2XDIV/0x15c49190*3 has been released.
>>> 2017/02/17 16:28:05.797 kid4| ctx: enter level  0:
>>> 'http://personal.avira-update.com/update/idx/weblocaldecider_sigver-win32-int-15.0.15.28.info.lz'
>>> 2017/02/17 16:28:05.797 kid4| 22,3| http.cc(339) cacheableReply: NO
>>> because e:=p2XDIV/0x15c49190*3 has been released.
>>> 2017/02/17 16:28:17.803 kid4| ctx: enter level  0:
>>> 'http://personal.avira-update.com/update/x_vdf_sigver/7.12.155.132_8.12.155.132/aevdf.dat.lz'
>>> 2017/02/17 16:28:17.803 kid4| 22,3| http.cc(339) cacheableReply: NO
>>> because e:=p2XDIV/0x6a233d0*3 has been released.
>>>
>>> It seems I'm not caching it too, but couldn't understand what "has been
>>> released" is referring too.
>> In this debugging context, "has been released" means that the response
>> was marked for removal from the cache some time earlier. It will be
>> delivered to the current client (or several concurrent clients in some
>> cases) but it will not be available to future clients.

>> These debugging lines do not tell us why or when that marking was
>> applied. It is possible that the response had some anti-caching
>> Cache-Control headers or was too big to cache, but these are just two
>> examples; there are lots of other possible reasons.

> When you say "some time earlier", you mean days?

Usually seconds or milliseconds (but, in theory, it could be a lot
longer than that, even days).


> I was using ALL,3 and cat cache.log |grep -C 10 avira-update |grep kid2

Sorry, I do not have enough information to answer "why" or "when".
Others on the list may be able to guide you further.

Alex.

_______________________________________________
squid-users mailing list
[hidden email]
http://lists.squid-cache.org/listinfo/squid-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: squid-avira-update-cache

splicelid
In reply to this post by Yuri Voinov
1487346706.878     60 10.3.2.254 TCP_MISS/200 265134 GET http://personal.avira-update.com/update/ave2_sigver/8.3.42.182/win32/int/aegen.dll.lz - ORIGINAL_DST/212.95.165.16 application/octet-stream

1487349903.649    129 10.3.2.254 TCP_TUNNEL/200 153 CONNECT ssldev.oes.avira.com:443 - ORIGINAL_DST/52.58.138.100 -

1487385532.212 43199639 10.3.2.254 TAG_NONE_TIMEDOUT/409 0 CONNECT ssldev.oes.avira.com:443 - HIER_NONE/- text/html;charset=utf-8

On Feb 17, 2017, at 16:52, Yuri Voinov <[hidden email]> wrote:

Any logs?


17.02.2017 17:43, [hidden email] пишет:
Hi all, I'm trying to cache "avira updates" with squid, but no luck...

my conf:
acl aviraupdate dstdomain .avira-update.com
range_offset_limit -1 aviraupdate
refresh_pattern -i avira-update.com/.*\.* 4320 80% 43200 reload-into-ims

any help ? 10x!


_______________________________________________
squid-users mailing list
[hidden email]
http://lists.squid-cache.org/listinfo/squid-users

--
Bugs to the Future
<0x613DEC46.asc>
_______________________________________________
squid-users mailing list
[hidden email]
http://lists.squid-cache.org/listinfo/squid-users

_______________________________________________
squid-users mailing list
[hidden email]
http://lists.squid-cache.org/listinfo/squid-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: squid-avira-update-cache

Amos Jeffries
Administrator
In reply to this post by Alex Rousskov
On 18/02/2017 9:31 a.m., Alex Rousskov wrote:

> On 02/17/2017 01:27 PM, Heiler Bemerguy wrote:
>> Em 17/02/2017 17:05, Alex Rousskov escreveu:
>>> On 02/17/2017 12:31 PM, Heiler Bemerguy wrote:
>>>> I've noticed this:
>>>>
>>>> 2017/02/17 16:28:05.632 kid4| ctx: enter level  0:
>>>> 'http://personal.avira-update.com/update/idx/localdecider_sigver-win32-int-13.0.1.12.info.lz'
>>>> 2017/02/17 16:28:05.632 kid4| 22,3| http.cc(339) cacheableReply: NO
>>>> because e:=p2XDIV/0x15c49190*3 has been released.
>>>> 2017/02/17 16:28:05.797 kid4| ctx: enter level  0:
>>>> 'http://personal.avira-update.com/update/idx/weblocaldecider_sigver-win32-int-15.0.15.28.info.lz'
>>>> 2017/02/17 16:28:05.797 kid4| 22,3| http.cc(339) cacheableReply: NO
>>>> because e:=p2XDIV/0x15c49190*3 has been released.
>>>> 2017/02/17 16:28:17.803 kid4| ctx: enter level  0:
>>>> 'http://personal.avira-update.com/update/x_vdf_sigver/7.12.155.132_8.12.155.132/aevdf.dat.lz'
>>>> 2017/02/17 16:28:17.803 kid4| 22,3| http.cc(339) cacheableReply: NO
>>>> because e:=p2XDIV/0x6a233d0*3 has been released.
>>>>
>>>> It seems I'm not caching it too, but couldn't understand what "has been
>>>> released" is referring too.
>>> In this debugging context, "has been released" means that the response
>>> was marked for removal from the cache some time earlier. It will be
>>> delivered to the current client (or several concurrent clients in some
>>> cases) but it will not be available to future clients.
>
>>> These debugging lines do not tell us why or when that marking was
>>> applied. It is possible that the response had some anti-caching
>>> Cache-Control headers or was too big to cache, but these are just two
>>> examples; there are lots of other possible reasons.
>
>> When you say "some time earlier", you mean days?
>
> Usually seconds or milliseconds (but, in theory, it could be a lot
> longer than that, even days).
>
>
>> I was using ALL,3 and cat cache.log |grep -C 10 avira-update |grep kid2
>
> Sorry, I do not have enough information to answer "why" or "when".
> Others on the list may be able to guide you further.
>

I usually point people to redbot.org at this point. But the report there
says the URL is cacheable so long as one is not using If-None-Match
headers. So it is not something the server is preventing, although ~5
min is a rather short TTL.


PS. The 'splicelid' person is showing access.log entries that indicate
they are intercepting traffic. So the Host-verify feature may be
involved with marking the objects as unsafe to cache. Avira was one
company I had a rather difficult discussion with about how their AV
client was using the Host header.

Amos

_______________________________________________
squid-users mailing list
[hidden email]
http://lists.squid-cache.org/listinfo/squid-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: squid-avira-update-cache

Amos Jeffries
Administrator
On 21/02/2017 10:00 p.m., FLASH FLASH wrote:

> this is part of my cache.log:
>
> 2017/02/21 10:54:47.908 kid1| 11,2| http.cc(2221) sendRequest: HTTP Server
> REQUEST:
> ---------
> GET /update/repair_sigver/1.0.25.18/win32/int/repair.rdf.lz HTTP/1.1
> Host: personal.avira-update.com
> User-Agent: @AUVI@1.3;AntiVir-NGUpd/15.0.24.143 (PERS; WKS; EN; AVE
> 8.3.42.182; VDF 8.12.155.244; Windows 10 Enterprise; ; Bulgaria;
> 4e083d762df61e49122f00e3758c65355687472f; 0000149996-AVHOE-0000001; BG;
> BUILD 15.0.24.146; 0; 1; 1; iexplore; 1;
> 309afc5503fe48febffe89e27e9390322a9f97f2; 0)
> Accept: */*
> Via: 1.1 router2 (squid/3.5.10)
> X-Forwarded-For: ...
> Cache-Control: no-cache, no-store, must-revalidate

There we go, the AV updater client (or maybe that 'router2' proxy?)
forbids cached content to be delivered as a response AND the response to
this request from being cached.

Which is kind of annoying since the server indicates the reply is
actually cacheable for at least a few minutes and HTTP/1.1 revalidation
performance features are supported. :-(

If router2 is under your control you could optimize a bit by erasing
that Cache-Control header from the AV updaters request before they are
sent on to the current Squid.

Amos

_______________________________________________
squid-users mailing list
[hidden email]
http://lists.squid-cache.org/listinfo/squid-users
Loading...