tree b34539ed4713c67ab7108944c9b61d29b7962781
parent 41afd9084e13fa834397f8f9925338223aaa4ed5
author Christopher Faulet <cfaulet@haproxy.com> 1658316244 +0200
committer Christopher Faulet <cfaulet@haproxy.com> 1658407814 +0200

BUG/MEDIUM: stconn: Only reset connect expiration when processing backend side

Since commit ae024ced0 ("MEDIUM: stream-int/stream: Use connect expiration
instead of SI expiration"), the connect expiration date is per-stream. So
there is only one expiration date instead of one per side, front and
back. So when a stream-connector is processed, we must test if it is a
frontend or a backend stconn before updating the connect expiration
date. Indeed, the frontend stconn must not reset the connect expiration
date.

This bug may have several side effect. One known bug is about peer sessions
blocked because the frontend peer applet is in ST_CLO state and its backend
connection is in ST_TAR state but without connect expiration date.

This patch should fix the issue #1791 and #1792. It must be backported to
2.6.