I see. How about varnishreplay as a workaround for this? How successful is it? anyone with a working example?
On Tue, Sep 4, 2012 at 10:27 PM, Tobias Eichelbrönner < [email protected]> wrote: > > The first hit from all users. > > as david said, the first hit by definition can not be in any cache. > > If you do not count a preloading request, you could make a rule that for > example the first request from outside 127.0.0.1 stores a trigger to a > variable > (https://github.com/varnish/libvmod-var) > so that the url will no longer be cached. > > But i really would like to read about any use case for that. > > > -- > LAMP solutions GmbH > Gostenhofer Hauptstrasse 35 > 90443 Nuernberg > > Amtsgericht Nuernberg: HRB 22366 > Geschaeftsfuehrer: Heiko Schubert > > Es gelten unsere allgemeinen Geschaeftsbedingungen. > http://www.lamp-solutions.de/agbs/ > > Telefon : 0911 / 376 516 0 > Fax : 0911 / 376 516 11 > E-Mail : [email protected] > Web : www.lamp-solutions.de > Facebook : http://www.facebook.com/LAMPsolutions > Twitter : http://twitter.com/#!/lampsolutions > > _______________________________________________ > varnish-misc mailing list > [email protected] > https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc >
_______________________________________________ varnish-misc mailing list [email protected] https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
