[Varnish] #1492: obj.hits is misleading after ban

Varnish varnish-bugs at varnish-cache.org
Fri May 2 13:17:21 CEST 2014

#1492: obj.hits is misleading after ban
 Reporter:  lkarsten  |      Owner:
     Type:  defect    |     Status:  new
 Priority:  normal    |  Milestone:
Component:  varnishd  |    Version:  trunk
 Severity:  normal    |   Keywords:
 In master and 4.0.0, the use of obj.hits is misleading after a ban.

 Expected result:
 obj.hits is reset after a ban removes an object.

 What happens:
 obj.hits is persisted as long as the ban is evaluated in the request

 Martin noted that if it is the ban lurker that cleans it out, and there
 are no other vary-ants, the oh is removed and the expected result happens.

 This was (to my knowledge) first reported by neurox on IRC.

 Test case that illustrates this is attached.

 Output from test case:
 **** c1    0.4 EXPECT resp.status (200) == "200" match
 ***  c1    0.4 expect
 **** c1    0.4 EXPECT resp.body (foo) == "foo" match
 ***  c1    0.4 expect
 ---- c1    0.4 EXPECT resp.http.hits (2) == "0" failed

Ticket URL: <https://www.varnish-cache.org/trac/ticket/1492>
Varnish <https://varnish-cache.org/>
The Varnish HTTP Accelerator

More information about the varnish-bugs mailing list