-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 18.03.16 19:42, Amos Jeffries пишет: > On 18/03/2016 11:49 p.m., Yuri Voinov wrote: >> Hi gents, >> >> I see strange behaviour for many URL's. >> >> Im my setups reload_into_ims is on globally. >> >> This time I see: >> >> - when I pressed Ctrl+F5 in browsers, for HTTP URLs >> >> TCP_REFRESH_UNMODIFIED/200 6447 GET >> http://icdn.lenta.ru/images/2016/03/17/09/20160317091221731/tabloid_8a08b3a372ff4499c0d95723ad4dc382.jpg >> - ORIGINAL_DST/81.19.76.10 image/jpeg >> >> occurs. >> >> - when I goes under HTTPS for the same URLs, i see TCP_MISS: >> >> TCP_MISS/200 6447 GET >> https://icdn.lenta.ru/images/2016/03/17/09/20160317091221731/tabloid_8a08b3a372ff4499c0d95723ad4dc382.jpg >> - ORIGINAL_DST/81.19.76.10 image/jpeg >> >> When I've test HTTPS URL with redbot, I've seen no problem with caching >> content: >> >> http://i.imgur.com/9dm7VWV.png >> >> As you can see, this site is news, with no private headers and no >> authentication. >> >> What's up? Is it bug or documented behaviour? I see absolutely no >> problem with caching either http or https versions of URL. >> > > What headers are on the two requests? root @ cthulhu /patch # wget -S http://icdn.lenta.ru/images/2016/03/17/09/20160317091221731/tabloid_8a08b3a372ff4499c0d95723ad4dc382.jpg - --2016-03-18 19:44:56-- http://icdn.lenta.ru/images/2016/03/17/09/20160317091221731/tabloid_8a08b3a372ff4499c0d95723ad4dc382.jpg Connecting to 127.0.0.1:3128... connected. Proxy request sent, awaiting response... HTTP/1.1 200 OK Content-Type: image/jpeg Content-Length: 5308 Accept-Ranges: bytes Server: nginx Date: Fri, 18 Mar 2016 10:50:33 GMT Last-Modified: Thu, 17 Mar 2016 06:12:22 GMT ETag: "56ea4ac6-14bc" Cache-Control: max-age=604800 Age: 10463 X-Cache: HIT from cthulhu X-Cache-Lookup: HIT from cthulhu:3128 Connection: keep-alive Length: 5308 (5.2K) [image/jpeg] Saving to: 'tabloid_8a08b3a372ff4499c0d95723ad4dc382.jpg' tabloid_8a08b3a372f 100%[=====================>] 5.18K --.-KB/s in 0s 2016-03-18 19:44:56 (70.4 MB/s) - 'tabloid_8a08b3a372ff4499c0d95723ad4dc382.jpg' saved [5308/5308] root @ cthulhu /patch # wget -S https://icdn.lenta.ru/images/2016/03/17/09/20160317091221731/tabloid_8a08b3a372ff4499c0d95723ad4dc382.jpg - --2016-03-18 19:45:18-- https://icdn.lenta.ru/images/2016/03/17/09/20160317091221731/tabloid_8a08b3a372ff4499c0d95723ad4dc382.jpg Connecting to 127.0.0.1:3128... connected. Proxy request sent, awaiting response... HTTP/1.1 200 OK Server: nginx Date: Fri, 18 Mar 2016 13:45:19 GMT Content-Type: image/jpeg Content-Length: 5308 Last-Modified: Thu, 17 Mar 2016 06:12:22 GMT Connection: keep-alive ETag: "56ea4ac6-14bc" Cache-Control: max-age=604800 Accept-Ranges: bytes Length: 5308 (5.2K) [image/jpeg] Saving to: 'tabloid_8a08b3a372ff4499c0d95723ad4dc382.jpg.1' tabloid_8a08b3a372f 100%[=====================>] 5.18K --.-KB/s in 0s 2016-03-18 19:45:19 (630 MB/s) - 'tabloid_8a08b3a372ff4499c0d95723ad4dc382.jpg.1' saved [5308/5308] root @ cthulhu /patch # wget -S https://icdn.lenta.ru/images/2016/03/17/09/20160317091221731/tabloid_8a08b3a372ff4499c0d95723ad4dc382.jpg - --2016-03-18 19:45:42-- https://icdn.lenta.ru/images/2016/03/17/09/20160317091221731/tabloid_8a08b3a372ff4499c0d95723ad4dc382.jpg Connecting to 127.0.0.1:3128... connected. Proxy request sent, awaiting response... HTTP/1.1 200 OK Server: nginx Date: Fri, 18 Mar 2016 13:45:42 GMT Content-Type: image/jpeg Content-Length: 5308 Last-Modified: Thu, 17 Mar 2016 06:12:22 GMT Connection: keep-alive ETag: "56ea4ac6-14bc" Cache-Control: max-age=604800 Accept-Ranges: bytes Length: 5308 (5.2K) [image/jpeg] Saving to: 'tabloid_8a08b3a372ff4499c0d95723ad4dc382.jpg.2' tabloid_8a08b3a372f 100%[=====================>] 5.18K --.-KB/s in 0s 2016-03-18 19:45:42 (695 MB/s) - 'tabloid_8a08b3a372ff4499c0d95723ad4dc382.jpg.2' saved [5308/5308] > > > Did the cache contain the https:// URL object prior to the refresh? Looks like this URL does not saving correctly: root @ cthulhu / # purge -e ^https\:\/\/icdn\.lenta\.ru\/images\/2016\/03\/17\/09\/20160317091221731\/tabloid_8a08b3a372ff4499c0d95723ad4dc382\.jpg$ ### Use at your own risk! No guarantees whatsoever. You were warned. ### WARNING: open "/data/cache/d1/00/C7/00018FD8": No such file or directory ^Creceived signal: Interrupt Cache entry exists, but it is empty. I don't want to say HTTPS completely not cached. Daily cache statistics show: # TCP-Request-protocol protocol request % hit-% sec/req Byte % hit-% kB/sec - ---------------- --------- ------ ------ ------- -------- ------ ------ ------- https: 48237 49.26 28.38 1.79 417322K 40.04 25.18 4.84 <secure> 34253 34.98 0.00 7.77 21148K 2.03 0.00 0.08 http: 14220 14.52 47.85 3.21 599333K 57.51 54.06 13.11 <error> 1209 1.23 0.17 23.16 4332K 0.42 0.59 0.15 - ---------------- --------- ------ ------ ------- -------- ------ ------ ------- Sum 97919 100.00 20.93 4.35 1042135K 100.00 41.17 2.51 As you can see, byte hit is significantly high for HTTP. But for HTTPS it two times lower in average. With agressive caching settings + store ID using. > > > Amos > > _______________________________________________ > squid-users mailing list > squid-users@xxxxxxxxxxxxxxxxxxxxx > http://lists.squid-cache.org/listinfo/squid-users -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJW7A0WAAoJENNXIZxhPexG+lIIAKBc/8z2B0HLcU255s848K4q jZ3FY+lnoYW1u/NjnEPSzV9NbokyDZMAmWTFdSV5oZ30klSKiLI4nGLiynlHW2z7 b5p0SmNdc9xY1YT3ZZXlEmvecfy6s1JIXvO/MRsG61F0uEdQESSYKP8k40Kur2Qw ZcOvms/JoSmAHJzZhdeYJIikEBdLEoCmAdUAf4rEvOzLp4zbTKw+yfYpv4mumMys TMT0PmE+pm19GrThP8ToQ8bK0l8SlTa0tO8SJSGXXdfoc3kznDifD0z9URkTAHZT BSqPhhhg+0q1WOs3ZQUek6EkwDs0QJfGukrmqarrpYnx/NhuFB3WBdI5PZbLHBg= =lmNM -----END PGP SIGNATURE-----
Attachment:
0x613DEC46.asc
Description: application/pgp-keys
_______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
