[Varnish] #860: Object not cached after force-refreshing

Varnish varnish-bugs at varnish-cache.org
Mon Feb 14 20:55:08 CET 2011

#860: Object not cached after force-refreshing
 Reporter:  pulse00              |        Type:  defect
   Status:  new                  |    Priority:  normal
Milestone:  Varnish 2.1 release  |   Component:  build 
  Version:  trunk                |    Severity:  normal
 Keywords:                       |  
 After force-refreshing an object from the backend, the resource is not
 cached anymore by varnish. I've tried multiple force-refresh techniques:



 What's happening before a resource is force-refreshed:

 1. vcl_recv is called

 2. vcl_hit | vcl_miss is called depending on the object's existence in the

 After one of the above techniques is used to force-refresh the cache for
 an object from the backend, only vcl_recv is called, but vcl_hit |
 vcl_miss is never called, although in vcl i specifically return(lookup)
 for the object. So the object is passed through to the backend and not put
 back in the cache.

 varnishd (varnish-2.1.5 SVN 0843d7a)

Ticket URL: <http://varnish-cache.org/trac/ticket/860>
Varnish <http://varnish-cache.org/>
The Varnish HTTP Accelerator

More information about the varnish-bugs mailing list