Le 26/09/2024 à 17:59, Luke Seelenbinder a écrit :
Hi again,
Sorry, it's the opposite direction of that. Varnish is the client in this case
(it sits behind a few other pieces, but that's the relevant for the bug). Full flow:
Client -> HAProxy -> Varnish -> HAProxy -> HAProxy Upstream application.
That make more sense? :)
It make more sens indeed. Thanks.
So HAproxy detects a server abort for an unknown reason since the 3.0.5. On
Varnish side, the response appears as truncated because it reports a 503 (At
least I guess it is what happens). At this stage, I guess it could be easier to
track the issue on Github.
Outside this bug, have you many unsuccessful termination states in your logs
(other than '----' in fact) ? If not, it could be possible to enable H1 traces
on error level. Let me know. In the mean time, I will review the 3.0.5 changes...
--
Christopher Faulet
