BUG/MEDIUM: stconn: Forward shutdown on write timeout only if it is forwardable
The commit b9c87f8082 ("BUG/MEDIUM: stconn/stream: Forward shutdown on write
timeout") introduced a regression. In sc_cond_forward_shut(), the write
timeout is considered too early to forward the shutdown. In fact, it is
always considered, even if the shutdown is not forwardable yet. It is of
course unexpected. It is especially an issue when a write timeout is
encountered on server side during the connection establishment. In this
case, if shutdown is forwarded too early on the client side, the connection
is closed before the 503 error sending.
So the write timeout must indeed be considered to forward the shutdown to
the underlying layer, but only if the shutdown is forwardable. Otherwise, we
should do nothing.
This patch should fix the issue #2404. It must be backported as far as 2.2.
(cherry picked from commit 7eb7ae283557d8467403b9db35605861a0870add)
Signed-off-by: Willy Tarreau <w@1wt.eu>
(cherry picked from commit 2b52339ac0fefd9561372e7a777f098dfa00ef1d)
Signed-off-by: Christopher Faulet <cfaulet@haproxy.com>
diff --git a/src/stconn.c b/src/stconn.c
index deb709f..3d4f8d1 100644
--- a/src/stconn.c
+++ b/src/stconn.c
@@ -512,15 +512,12 @@
*/
static inline int sc_cond_forward_shut(struct stconn *sc)
{
- /* Foward the shutdown if an write error occurred on the input channel */
- if (sc_ic(sc)->flags & CF_WRITE_TIMEOUT)
- return 1;
/* The close must not be forwarded */
if (!(sc->flags & (SC_FL_EOS|SC_FL_ABRT_DONE)) || !(sc->flags & SC_FL_NOHALF))
return 0;
- if (!channel_is_empty(sc_ic(sc))) {
+ if (!channel_is_empty(sc_ic(sc)) && !(sc_ic(sc)->flags & CF_WRITE_TIMEOUT)) {
/* the shutdown cannot be forwarded now because
* we should flush outgoing data first. But instruct the output
* channel it should be done ASAP.