[Varnish] #247: Varnish sends 304 header for ESI pages although some of the included objects might have changed

[Varnish]

#247: Varnish sends 304 header for ESI pages although some of the included
objects might have changed
----------------------+-----------------------------------------------------
 Reporter:  peter     |        Owner:  phk  
     Type:  defect    |       Status:  new  
 Priority:  lowest    |    Milestone:  Later
Component:  varnishd  |      Version:  trunk
 Severity:  normal    |   Resolution:       
 Keywords:            |  
----------------------+-----------------------------------------------------
Comment (by eugaia):

 In my opinion, VCL should allow for telling the client how to cache
 objects in a way that can be set independently of Varnish's cache.  This
 could be done in at least three ways I can think of (off the top of my
 head, quickly):

 1) Last modified time (as sky suggests, this should logically be set to
 the youngest cached object)
 2) Cached on the client for TTL (as phk says, this should logically be set
 to the shortest TTL of any cached objects)
 3) A different 'external' TTL (this could be set independently to any of
 the objects that are part of the page and independently of Varnish's cache
 of the page - the obj.ttl value).

 I would expect (3) to be used only in a few number of cases if the other
 two are properly implemented, but there may be some specific cases where
 someone might wish to set an external cache time greater than the minimum
 objects TTL's time as a design decision.

-- 
Ticket URL: <http://varnish.projects.linpro.no/ticket/247#comment:4>
Varnish <http://varnish.projects.linpro.no/>
The Varnish HTTP Accelerator