[squid-users] Squid reverse-proxy. How it decides when to refresh?

Alexander Lazarev gummeah at gmail.com
Thu Aug 31 17:26:50 UTC 2017


Thank you for reply!
I still don't understand what's happening.
I create file 1.txt with a little bit of text data. Request it with curl.
Web-server returns it without any cache related headers to squid, squid
returns it to me. Getting it with curl one more time, squid serves it
straight from cache without validation(no entries in log on origin server).
I create one more file 2.txt with some data. Do same things, same headers
in response. Second response from squid is from cache but validated from
origin server(i see 304 in origin server logs).
What could be wrong?
I have thought maybe squid applying heuristic freshness, but i didn't see
any warnings in headers.
Maybe some sort of a bug?

On Fri, Aug 25, 2017 at 6:18 PM, Amos Jeffries <squid3 at treenet.co.nz> wrote:

> On 26/08/17 00:37, Alexander Lazarev wrote:
>
>> Hello guys!
>> I'm using squid as a reverse-proxy. And I can't understand how squid
>> decides when to check for fresh version of file from origin server.
>> It looks like for some documents it sends 'If-Modified-Since' or similar
>> headers and if it gets 304, it serves file from cache. And for some
>> documents it doesn't check for fresh version and always serves from cache.
>> > I was testing that with curl without any additional headers.
>> Can some explain how that works or where I can read about that in detail?
>>
>
> The HTTP specification RFC 723x series was re-written to be a lot more
> easily understood, so those are probably the best place to read up about it.
>
> The features you are asking about are covered in:
>
> Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests
>  <https://tools.ietf.org/html/rfc7232>
>
> Hypertext Transfer Protocol (HTTP/1.1): Caching
>  <https://tools.ietf.org/html/rfc7234>
>
>
> And is it possible to make squid always check for fresh version before
>> serving from cache?
>>
>
> It does when needed. The situation may be clearer after reading the above.
>
> Amos
> _______________________________________________
> squid-users mailing list
> squid-users at lists.squid-cache.org
> http://lists.squid-cache.org/listinfo/squid-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squid-cache.org/pipermail/squid-users/attachments/20170831/4283a2d4/attachment-0001.html>


More information about the squid-users mailing list