[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.
This commit is contained in:
Willy Tarreau 2010-06-06 16:48:26 +02:00
parent 13c29dee21
commit c00cdc2eb0
2 changed files with 6 additions and 7 deletions

View File

@ -4998,7 +4998,7 @@ stick-table type {ip | integer | string [len <length>] } size <size>
[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 @@ stick-table type {ip | integer | string [len <length>] } size <size>
"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.

View File

@ -4877,7 +4877,7 @@ int check_config_validity()
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 @@ int check_config_validity()
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,7 +5471,6 @@ out_uri_auth_compat:
* other proxies.
*/
for (curproxy = proxy; curproxy; curproxy = curproxy->next)
if (curproxy->cap & PR_CAP_BE)
stktable_init(&curproxy->table);
/*