[MINOR] stick_table: enable it for frontends too
A frontend may very well host a stick-table. In fact it will be useful
with connection throttling.
diff --git a/doc/configuration.txt b/doc/configuration.txt
index f2275f7..8366636 100644
--- a/doc/configuration.txt
+++ b/doc/configuration.txt
@@ -4998,7 +4998,7 @@
[expire <expire>] [nopurge] [store <data_type>]*
Configure the stickiness table for the current backend
May be used in sections : defaults | frontend | listen | backend
- no | no | yes | yes
+ no | yes | yes | yes
Arguments :
ip a table declared with "type ip" will only store IPv4 addresses.
@@ -5059,8 +5059,8 @@
"server_id" type is also supported but it's only for internal
use for stick and store directives.
- The is only one stick-table per backend. At the moment of writing this doc,
- it does not seem useful to have multiple tables per backend. If this happens
+ There is only one stick-table per proxy. At the moment of writing this doc,
+ it does not seem useful to have multiple tables per proxy. If this happens
to be required, simply create a dummy backend with a stick-table in it and
reference it.
diff --git a/src/cfgparse.c b/src/cfgparse.c
index d472f99..cf9a000 100644
--- a/src/cfgparse.c
+++ b/src/cfgparse.c
@@ -4877,7 +4877,7 @@
curproxy->be_rsp_ana |= AN_RES_STORE_RULES;
if (mrule->table.name)
- target = findproxy(mrule->table.name, PR_CAP_BE);
+ target = findproxy(mrule->table.name, 0);
else
target = curproxy;
@@ -4910,7 +4910,7 @@
curproxy->be_rsp_ana |= AN_RES_STORE_RULES;
if (mrule->table.name)
- target = findproxy(mrule->table.name, PR_CAP_BE);
+ target = findproxy(mrule->table.name, 0);
else
target = curproxy;
@@ -5471,8 +5471,7 @@
* other proxies.
*/
for (curproxy = proxy; curproxy; curproxy = curproxy->next)
- if (curproxy->cap & PR_CAP_BE)
- stktable_init(&curproxy->table);
+ stktable_init(&curproxy->table);
/*
* Recount currently required checks.