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

[Amos Jeffries]

On 19/03/2016 11:50 p.m., Yuri Voinov wrote:
> 
> Well, here is it:
> 
<snip>
> 
> GET
> http://icdn.lenta.ru/images/2016/03/17/09/20160317091221731/tabloid_8a08b3a372ff4499c0d95723ad4dc382.jpg
> HTTP/1.1
> User-Agent: Wget/1.16.3 (solaris2.10)
> Accept: */*
> Accept-Encoding: identity
> Host: icdn.lenta.ru
> Connection: Keep-Alive
> Proxy-Connection: Keep-Alive
>
<snip>
> 
> GET
> /images/2016/03/17/09/20160317091221731/tabloid_8a08b3a372ff4499c0d95723ad4dc382.jpg
> HTTP/1.1
> User-Agent: Wget/1.16.3 (solaris2.10)
> Accept: */*
> Accept-Encoding: identity
> Host: icdn.lenta.ru
> Connection: Keep-Alive
> Proxy-Connection: Keep-Alive
> 


Neither of those requests contain Cache-Control: max-age=0 (aka
"reload") from the client.

So the directive reload_into_ims is not having any relevance. And thus
no effect.

It kind of makes sense - most clients still assume that HTTPS is
end-to-end and not having any proxy caches along the way. Not that the
assumption was ever true.

Amos