Re: [squid-users] Directives ignore-private and override-expire not working Squid 3.2 and 3.3

Hi, Eliezer Croitoru

I already sent the header in the first email. Is this the information you want ?
========= Squid 3.3.x ============
HTTP/1.1 200 OK
Cache-Control: private
Content-Length: 117991
Content-Type: text/html; charset=utf-8
Expires: Thu, 21 Nov 2013 03:12:14 GMT
Server: Microsoft-IIS/7.5
Date: Thu, 21 Nov 2013 03:12:15 GMT
X-Cache: MISS from localhost.localdomain
Connection: close

And after Amos's reply I check again the header of Squid-3.1

========= Squid 3.1.x ============
HTTP/1.0 200 OK
Cache-Control: private
Content-Type: text/html; charset=utf-8
Expires: Tue, 26 Nov 2013 05:00:03 GMT
Server: Microsoft-IIS/7.5
Date: Tue, 26 Nov 2013 05:00:04 GMT
Content-Length: 117904
Age: 64
Warning: 110 squid/3.1.23 "Response is stale" (confused here too !)
X-Cache: HIT from localhost.localdomain
Connection: close

In both case I used the same directives ignore-private and
override-expire and same origin server. Squids also built in same
server, the difference is only http service ports.

Still don't know why squid 3.3 and 3.2 can't ignore-private and
override-expire header.

Best Regards,
Kien Le

On Tue, Nov 26, 2013 at 11:10 AM, Amos Jeffries <squid3_at_treenet.co.nz> wrote:
> On 26/11/2013 4:35 p.m., Eliezer Croitoru wrote:
>> Hey,
>>
>> Just to make sure you have taken a small look at the headers.
>> The headers states that at almost the same time the request was asked it
>> was expired.
>> I have not seen the Request headers and I cannot tell you why it is like
>> that but it seems like there is a reason for that.
>
> Usually this is done on resources where the webmaster knows what they
> are doing and is completely confident that the data MUST NOT be stored.
> You know, the stuff the contains *private* user details and such.
>
> Expires: header causes HTTP/1.0 caches to remove the content immediately
> (or not store in the first place).
>
> Cache-Control:private does the same thing for HTTP/1.1 caches except for
> browsers. Which in HTTP/1.1 are allowed to store private data unless the
> "Cache-Control:no-store" or "Expires:" controls are also used.
>
>
> Amos
>

-- 
Best Regards,
Ki�n L�