This reverts commit
bd48e26a747016acfddce2929443f84fdb9e6997.
Indeed, since commit
b71d27e253 ("BUG/MINOR: stream: Fix custom max-retries
initialization when setting backend"), the proxy conn_retries parameter is
now taken again into account for proxies lacking the CAP_FE capability.
Let's remove comments that says otherwise.
{
fe->mode = PR_MODE_PEERS;
fe->maxconn = 0;
- fe->conn_retries = CONN_RETRIES; /* FIXME ignored since 91e785ed
- * ("MINOR: stream: Rely on a per-stream max connection retries value")
- * If this is really expected this should be set on the stream directly
- * because the proxy is not part of the main proxy list and thus
- * lacks the required post init for this setting to be considered
- */
+ fe->conn_retries = CONN_RETRIES;
fe->timeout.connect = MS_TO_TICKS(1000);
fe->timeout.client = MS_TO_TICKS(5000);
fe->timeout.server = MS_TO_TICKS(5000);
void resolvers_setup_proxy(struct proxy *px)
{
px->maxconn = 0;
- px->conn_retries = 1; /* FIXME ignored since 91e785ed
- * ("MINOR: stream: Rely on a per-stream max connection retries value")
- * If this is really expected this should be set on the stream directly
- * because the proxy is not part of the main proxy list and thus
- * lacks the required post init for this setting to be considered
- */
+ px->conn_retries = 1;
px->timeout.server = TICK_ETERNITY;
px->timeout.client = TICK_ETERNITY;
px->timeout.connect = 1000; // by default same than timeout.resolve
{
px->mode = PR_MODE_SYSLOG;
px->maxconn = 0;
- px->conn_retries = 1; /* FIXME ignored since 91e785ed
- * ("MINOR: stream: Rely on a per-stream max connection retries value")
- * If this is really expected this should be set on the stream directly
- * because the proxy lacks the CAP_FE so this setting is not considered
- */
+ px->conn_retries = 1;
px->timeout.server = TICK_ETERNITY;
px->timeout.client = TICK_ETERNITY;
px->timeout.connect = TICK_ETERNITY;