tree 362e390a26faaec5c02c9a9ca4e29074804ee2a5
parent 3e34ac7d09c33f62c52bc7ca0df18310b1afcff4
author Christopher Faulet <cfaulet@haproxy.com> 1578576673 +0100
committer Christopher Faulet <cfaulet@haproxy.com> 1578580746 +0100

BUG/MINOR: stream-int: Don't trigger L7 retry if max retries is already reached

When an HTTP response is received, at the stream-interface level, if a L7 retry
must be triggered because of the status code, the response is trashed and a read
error is reported on the response channel. Then the stream handles this error
and perform the retry. Except if the maximum connection retries is reached. In
this case, an error is reported. Because the server response was already trashed
by the stream-interface, a generic 502 error is returned to the client instead
of the server's one.

Now, the stream-interface triggers a L7 retry only if the maximum connection
retries is not already reached. Thus, at the end, the last server's response is
returned.

This patch must be backported to 2.1 and 2.0. It should fix the issue #439.