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

[Amos Jeffries]

On 19/03/2016 3:13 a.m., Yuri Voinov wrote:
> 18.03.16 19:42, Amos Jeffries пишет:
> 
>> 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'
> 

Thats the reply headers.

reload_into_ims is about altering request headers.

Amos