[squid-users] Does reload_into_ims not effective for HTTPS?

Amos Jeffries squid3 at treenet.co.nz
Thu Mar 24 11:38:28 UTC 2016


On 24/03/2016 4:11 a.m., Yuri Voinov wrote:
> 
> i.e.,  for example,
> 
> request_header_access Cache-Control deny all
> request_header_access Cache-Control: max-age=0

Only alters the *outbound* from Squid to server.

> 
> will raise cache hit ratio in conjunction with reload_into_ims on, right?
> 

No.

"Cache-Control: max-age=0" from the client forces a MISS.

reload_into_ims takes that forced-MISS and raises it half-way back
towards being a HIT.

If the client had sent nothing it would have been a HIT or IMS / REFRESH
anyway (if cached). So best-case is no change. Average-case is
downgrading HIT to IMS / REFRESH. And worst-case is the IMS getting back
a complete new copy (aka identical to a MISS).


 => all you can do by playing around with these is make the HIT ratio worse.

Amos


More information about the squid-users mailing list