In message <cababnj7os8i3nom8aunkqo026g2338pqvjym5uvhhg4u56f...@mail.gmail.com>
, Kacper Wysocki writes:
>But the reply to the client may fail or hit an exception at any point,
>both from the source side of the data (backend timeout) and the sink
>side (client timeout), and being able to do something in VCL on these
>conditions is gold.
What would you do ? The half-baked reponse being half-sent to the
client cannot be recovered or salvaged in any way ?
> As far as I can understand the problem it's that the introduction of
>streaming makes it real hard to do a callback?
It's more that there is nothing the call-back can do, the damage is
done and there's nothing sensible we can do, but a cleanup.
>There are some use cases for vcl_error are not being considered here.
They are considered, but I may not have explained it well enough:
Instead of vcl_error{}, you will use vcl_deliver{}, and in vcl_deliver{}
you can build synthetic responses.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[email protected] | 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
[email protected]
https://www.varnish-cache.org/lists/mailman/listinfo/varnish-dev
