mirror of
http://git.haproxy.org/git/haproxy.git/
synced 2025-01-20 20:50:44 +00:00
[MINOR] acl: add ability to check for internal response-only parameters
Some parameters are known to the response only (eg: the server which processed it). Let's have a flag for that.
This commit is contained in:
parent
17af419a01
commit
930bd6b763
@ -151,6 +151,9 @@ enum {
|
|||||||
ACL_USE_HDR_VOLATILE = 1 << 22, /* volatile request or response header (eg: cookie) */
|
ACL_USE_HDR_VOLATILE = 1 << 22, /* volatile request or response header (eg: cookie) */
|
||||||
ACL_USE_HDR_ANY = (ACL_USE_HDR_CACHEABLE | ACL_USE_HDR_VOLATILE),
|
ACL_USE_HDR_ANY = (ACL_USE_HDR_CACHEABLE | ACL_USE_HDR_VOLATILE),
|
||||||
|
|
||||||
|
/* This one indicates that we need an internal parameter known in the response only */
|
||||||
|
ACL_USE_RTR_INTERNAL = 1 << 23, /* volatile response information */
|
||||||
|
|
||||||
/* information which remains during response */
|
/* information which remains during response */
|
||||||
ACL_USE_REQ_PERMANENT = (ACL_USE_TCP4_PERMANENT | ACL_USE_TCP6_PERMANENT | ACL_USE_TCP_PERMANENT |
|
ACL_USE_REQ_PERMANENT = (ACL_USE_TCP4_PERMANENT | ACL_USE_TCP6_PERMANENT | ACL_USE_TCP_PERMANENT |
|
||||||
ACL_USE_L6REQ_PERMANENT | ACL_USE_L7REQ_PERMANENT),
|
ACL_USE_L6REQ_PERMANENT | ACL_USE_L7REQ_PERMANENT),
|
||||||
@ -168,7 +171,7 @@ enum {
|
|||||||
ACL_USE_L7_ANY = (ACL_USE_L7REQ_ANY | ACL_USE_L7RTR_ANY | ACL_USE_HDR_ANY),
|
ACL_USE_L7_ANY = (ACL_USE_L7REQ_ANY | ACL_USE_L7RTR_ANY | ACL_USE_HDR_ANY),
|
||||||
|
|
||||||
/* any type of response information */
|
/* any type of response information */
|
||||||
ACL_USE_RTR_ANY = (ACL_USE_L6RTR_ANY | ACL_USE_L7RTR_ANY),
|
ACL_USE_RTR_ANY = (ACL_USE_L6RTR_ANY | ACL_USE_L7RTR_ANY | ACL_USE_RTR_INTERNAL),
|
||||||
|
|
||||||
/* some flags indicating if a keyword supports exact pattern matching,
|
/* some flags indicating if a keyword supports exact pattern matching,
|
||||||
* so that patterns may be arranged in lookup trees. Let's put those
|
* so that patterns may be arranged in lookup trees. Let's put those
|
||||||
|
Loading…
Reference in New Issue
Block a user