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
