with github issue #627 we've had at least one report of someone using retry-on
with mode tcp. Olivier fixed the crash, and I propose the attached patch to
better document that retry-on is only valid when used with mode http and
ignored otherwise.

>From e030ea97758cc8b6af5f655637137230e9a1791f Mon Sep 17 00:00:00 2001
From: Jerome Magnin <jmag...@haproxy.com>
Date: Wed, 13 May 2020 20:09:57 +0200
Subject: [PATCH] DOC: retry-on can only be used with mode http

The documentation for retry-on hints at it being meant to be used
in conjuction with mode http, but since we've a had bug report
involving mode tcp and retry-on, lets make it explicit in the
documentation that it only works with mode http and will be
ignored otherwise.
 doc/configuration.txt | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/doc/configuration.txt b/doc/configuration.txt
index 7594992b4..3071c655d 100644
--- a/doc/configuration.txt
+++ b/doc/configuration.txt
@@ -8749,7 +8749,9 @@ retries <value>
 retry-on [list of keywords]
-  Specify when to attempt to automatically retry a failed request
+  Specify when to attempt to automatically retry a failed request.
+  This setting is only valid when "mode" is set to http and is silently ignored
+  otherwise.
   May be used in sections:    defaults | frontend | listen | backend
                                  yes   |    no    |   yes  |   yes
   Arguments :

Reply via email to