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

[Varnish]

#1492: obj.hits is misleading after ban
----------------------+----------------------------------------
 Reporter:  lkarsten  |       Owner:  Poul-Henning Kamp <phk@…>
     Type:  defect    |      Status:  closed
 Priority:  normal    |   Milestone:
Component:  varnishd  |     Version:  trunk
 Severity:  normal    |  Resolution:  fixed
 Keywords:            |
----------------------+----------------------------------------
Changes (by Poul-Henning Kamp <phk@…>):

 * status:  new => closed
 * owner:   => Poul-Henning Kamp <phk@…>
 * resolution:   => fixed


Comment:

 In [278d90fdc0008a55405550482ccf9bc4d74f18dc]:
 {{{
 #!CommitTicketReference repository=""
 revision="278d90fdc0008a55405550482ccf9bc4d74f18dc"
 Update the documentation for obj.hits to reflect code reality.

 In 4.x we changed obj.hits to be read-only, and to count all variants
 under the same hash-key (= same objhdr).

 Since we cannot trivially tell if a ban hits all Vary: values or
 just some of them, there is no sane heuristic to fiddle obj.hits
 on bans that would Do The Right Thing.

 Fixes #1492
 }}}

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