Re: [squid-users] Re: Sibling cache peer for a HTTPS reverse proxy

From: Amos Jeffries <squid3_at_treenet.co.nz>
Date: Tue, 29 Jul 2014 03:47:33 +1200

On 29/07/2014 3:39 a.m., Makson wrote:
> Amos Jeffries wrote
>> 1) broken cacheability headers.
>> The Expires: header says (Date: + 360 days), and s-maxage says 360days
>> BUT ... Last-Modified says 1970. So Last-Modified + s-maxage is already
>> expired.
>> NP: this is not breaking Squid which still (incorrectly) uses Expires
>> header in preference to s-maxage. But when we fix that bug this server
>> will start to MISS constantly.
>
> So this is caused by the application? It is made by IBM, if you fix this
> bug, i guess we need to keep using the older version of Squid.
>
>
> Amos Jeffries wrote
>> Does the matching "HTTP Server REQUEST" to the parent peer for the
>> eclipse transaction contain an If-Modified-Since and/or If-Match header?
>
> Sorry, i didn't get that, would you please explain me in more detail?

There is a HTTP request to the parent server leading to that reply you
posted the headers for. What is the request headers?

Amos
Received on Mon Jul 28 2014 - 15:47:42 MDT

This archive was generated by hypermail 2.2.0 : Tue Jul 29 2014 - 12:00:05 MDT