In message <5ebb67dc-b916-4bc2-9c9a-10205edf7...@crucially.net>, Artur Bergman writes:
>Couple of points. > >I agree with all, except I think they should be delivered through = >vcl_deliver, or you have to duplicate header logic in both of them. Presently we allow limited obj.* access in vcl_deliver{}, but that's actually limited to the obj.hits and obj.lastuse variables which are under dispute for causing write-backs to object storage. So if we eliminate those two, using vcl_deliver{} should be feasible. >Regarding ESI, as long as an ESI can have an fragment be a synth reply, = >I am happy. It can, but the synth reply cannot be ESI parsed. I did consider the alternative, where you call synth() from vcl_recv{} and then go from there to vcl_fetch{}, in essense making synth{} a virtual backend. Would that be better ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. _______________________________________________ varnish-dev mailing list varnish-dev@varnish-cache.org https://www.varnish-cache.org/lists/mailman/listinfo/varnish-dev