Re: If refresh_pattern only extends expiration, how to force time-to-live in Squid code?

I'm using a customized version of Squid 2.4 STABLE6. But nothing
seems to be customized in refresh.c, except for my own recent swap of
age and expires checks (as recommended).

Probably the expires header is added in some other place, it's just
difficult to figure out exactly where in the code and how it is
controlled.

On Wed, Sep 2, 2009 at 1:29 PM, Henrik
Nordstrom<henrik_at_henriknordstrom.net> wrote:
> ons 2009-09-02 klockan 12:42 -0700 skrev Guy Bashkansky:
>
>> Now I see the Expires header having a value in the past, which may
>> confuse clients and caches further down the chain.
>> Scenario: origin returns max-age=900 (15 min) and refresh_pattern
>> overrides expire to 24 hours, what do the headers to the client look
>> like?
>>
>> On the first request (cache-miss), the Expires header is not added to
>> the response sent to client.
>> On subsequent cache-hits the Expires header is added to the response
>> sent to client. (Why this artifact?)
>
> Is it? Should not, at least not unless you run 2.7 with the
> act-as-origin option..
>
>> The Expires header is set to time the object was received from the
>> origin plus the value in the Max-age header.
>
> odd..
>
> Regards
> Henrik
>
>
Received on Wed Sep 02 2009 - 20:43:21 MDT