RepoMirrors
/
haproxy
mirror of http://git.haproxy.org/git/haproxy.git/
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
haproxy/reg-tests/checks/http-check-expect.vtc

65 lines
2.3 KiB
Plaintext
Raw Permalink Normal View History

MEDIUM: checks: Support matching on headers for http-check expect rules It is now possible to add http-check expect rules matching HTTP header names and values. Here is the format of these rules: http-check expect header name [ -m <meth> ] <name> [log-format] \ [ value [ -m <meth> ] <value> [log-format] [full] ] the name pattern (name ...) is mandatory but the value pattern (value ...) is optionnal. If not specified, only the header presence is verified. <meth> is the matching method, applied on the header name or the header value. Supported matching methods are: * "str" (exact match) * "beg" (prefix match) * "end" (suffix match) * "sub" (substring match) * "reg" (regex match) If not specified, exact matching method is used. If the "log-format" option is used, the pattern (<name> or <value>) is evaluated as a log-format string. This option cannot be used with the regex matching method. Finally, by default, the header value is considered as comma-separated list. Each part may be tested. The "full" option may be used to test the full header line. Note that matchings are case insensitive on the header names.
2020-05-05 08:47:36 +00:00
varnishtest "Health-checks: some http-check expect tests"
feature ignore_unknown_macro
#REQUIRE_VERSION=2.2
#REGTEST_TYPE=slow
# This script tests http-check expect rules.
server s1 {
rxreq
expect req.method == OPTIONS
expect req.url == /
expect req.proto == HTTP/1.0
txresp -status 202 \
-hdr "x-test1: true, next value" \
-hdr "x-test2: true, begin-value, value-end, value-sub-string, value-reg-123ABC" \
-hdr "x-begin-test: 1" \
-hdr "x-test-end: 1" \
-hdr "x-sub-test: 1" \
-hdr "x-reg-test1: 1" \
-hdr "x-hdr-name: x-test1"
} -start
syslog S1 -level notice {
recv
expect ~ "[^:\\[ ]\\[${h1_pid}\\]: Health check for server be1/srv succeeded.*code: 202"
} -start
haproxy h1 -conf {
defaults
mode http
REGTESTS: extend the default I/O timeouts and make them overridable With the CI occasionally slowing down, we're starting to see again some spurious failures despite the long 1-second timeouts. This reports false positives that are disturbing and doesn't provide as much value as this could. However at this delay it already becomes a pain for developers to wait for the tests to complete. This commit adds support for the new environment variable HAPROXY_TEST_TIMEOUT that will allow anyone to modify the connect, client and server timeouts. It was set to 5 seconds by default, which should be plenty for quite some time in the CI. All relevant values that were 200ms or above were replaced by this one. A few larger values were left as they are special. One test for the set-timeout action that used to rely on a fixed 1-sec value was extended to a fixed 5-sec, as the timeout is normally not reached, but it needs to be known to compare the old and new values.
2021-11-18 16:46:22 +00:00
timeout client "${HAPROXY_TEST_TIMEOUT-5s}"
timeout server "${HAPROXY_TEST_TIMEOUT-5s}"
timeout connect "${HAPROXY_TEST_TIMEOUT-5s}"
MEDIUM: checks: Support matching on headers for http-check expect rules It is now possible to add http-check expect rules matching HTTP header names and values. Here is the format of these rules: http-check expect header name [ -m <meth> ] <name> [log-format] \ [ value [ -m <meth> ] <value> [log-format] [full] ] the name pattern (name ...) is mandatory but the value pattern (value ...) is optionnal. If not specified, only the header presence is verified. <meth> is the matching method, applied on the header name or the header value. Supported matching methods are: * "str" (exact match) * "beg" (prefix match) * "end" (suffix match) * "sub" (substring match) * "reg" (regex match) If not specified, exact matching method is used. If the "log-format" option is used, the pattern (<name> or <value>) is evaluated as a log-format string. This option cannot be used with the regex matching method. Finally, by default, the header value is considered as comma-separated list. Each part may be tested. The "full" option may be used to test the full header line. Note that matchings are case insensitive on the header names.
2020-05-05 08:47:36 +00:00
option log-health-checks
backend be1
log ${S1_addr}:${S1_port} len 2048 local0
option httpchk
http-check expect status 200-399
MINOR: checks: Simplify matching on HTTP headers in HTTP expect rules Extra parameters on http-check expect rules, for the header matching method, to use log-format string or to match full header line have been removed. There is now separate matching methods to match a full header line or to match each comma-separated values. "http-check expect fhdr" must be used in the first case, and "http-check expect hdr" in the second one. In addition, to match log-format header name or value, "-lf" suffix must be added to "name" or "value" keyword. For intance: http-check expect hdr name "set-cookie" value-lf -m beg "sessid=%[var(check.cookie)]" Thanks to this changes, each parameter may only be interpreted in one way.
2020-05-05 18:23:13 +00:00
http-check expect hdr name "x-test1"
http-check expect hdr name -m str "X-Test2"
http-check expect hdr name -m beg "X-Begin-"
http-check expect hdr name -m end "-End"
http-check expect hdr name -m sub "-Sub-"
http-check expect hdr name -m reg "^[a-z]+-Reg-[a-z]+[0-9]\$"
MEDIUM: checks: Remove dedicated sample fetches and use response ones instead All sample fetches in the scope "check." have been removed. Response sample fetches must be used instead. It avoids keyword duplication. So, for instance, res.hdr() must be now used instead of check.hdr(). To do so, following sample fetches have been added on the response : * res.body, res.body_len and res.body_size * res.hdrs and res.hdrs_bin Sample feches dealing with the response's body are only useful in the health checks context. When called from a stream context, there is no warranty on the body presence. There is no option to wait the response's body.
2020-05-05 15:46:34 +00:00
http-check set-var(check.hdr_name) res.fhdr(x-hdr-name)
MINOR: checks: Simplify matching on HTTP headers in HTTP expect rules Extra parameters on http-check expect rules, for the header matching method, to use log-format string or to match full header line have been removed. There is now separate matching methods to match a full header line or to match each comma-separated values. "http-check expect fhdr" must be used in the first case, and "http-check expect hdr" in the second one. In addition, to match log-format header name or value, "-lf" suffix must be added to "name" or "value" keyword. For intance: http-check expect hdr name "set-cookie" value-lf -m beg "sessid=%[var(check.cookie)]" Thanks to this changes, each parameter may only be interpreted in one way.
2020-05-05 18:23:13 +00:00
http-check expect hdr name-lf -m str "%[var(check.hdr_name)]"
http-check expect hdr name-lf -m str "%[res.fhdr(x-hdr-name)]"
MEDIUM: checks: Support matching on headers for http-check expect rules It is now possible to add http-check expect rules matching HTTP header names and values. Here is the format of these rules: http-check expect header name [ -m <meth> ] <name> [log-format] \ [ value [ -m <meth> ] <value> [log-format] [full] ] the name pattern (name ...) is mandatory but the value pattern (value ...) is optionnal. If not specified, only the header presence is verified. <meth> is the matching method, applied on the header name or the header value. Supported matching methods are: * "str" (exact match) * "beg" (prefix match) * "end" (suffix match) * "sub" (substring match) * "reg" (regex match) If not specified, exact matching method is used. If the "log-format" option is used, the pattern (<name> or <value>) is evaluated as a log-format string. This option cannot be used with the regex matching method. Finally, by default, the header value is considered as comma-separated list. Each part may be tested. The "full" option may be used to test the full header line. Note that matchings are case insensitive on the header names.
2020-05-05 08:47:36 +00:00
MINOR: checks: Simplify matching on HTTP headers in HTTP expect rules Extra parameters on http-check expect rules, for the header matching method, to use log-format string or to match full header line have been removed. There is now separate matching methods to match a full header line or to match each comma-separated values. "http-check expect fhdr" must be used in the first case, and "http-check expect hdr" in the second one. In addition, to match log-format header name or value, "-lf" suffix must be added to "name" or "value" keyword. For intance: http-check expect hdr name "set-cookie" value-lf -m beg "sessid=%[var(check.cookie)]" Thanks to this changes, each parameter may only be interpreted in one way.
2020-05-05 18:23:13 +00:00
http-check expect fhdr name "x-test1" value "true, next value"
http-check expect hdr name "x-test2" value -m str "true"
http-check expect hdr name -m beg "x-test" value -m beg "begin-"
http-check expect hdr name -m beg "x-test" value -m end "-end"
http-check expect hdr name -m beg "x-test" value -m sub "-sub-"
http-check expect hdr name -m beg "x-test" value -m reg "^value-reg-[A-Z0-9]+\$"
http-check expect fhdr name -m beg "x-test" value -m reg "value-reg-[A-Z0-9]+"
MEDIUM: checks: Support matching on headers for http-check expect rules It is now possible to add http-check expect rules matching HTTP header names and values. Here is the format of these rules: http-check expect header name [ -m <meth> ] <name> [log-format] \ [ value [ -m <meth> ] <value> [log-format] [full] ] the name pattern (name ...) is mandatory but the value pattern (value ...) is optionnal. If not specified, only the header presence is verified. <meth> is the matching method, applied on the header name or the header value. Supported matching methods are: * "str" (exact match) * "beg" (prefix match) * "end" (suffix match) * "sub" (substring match) * "reg" (regex match) If not specified, exact matching method is used. If the "log-format" option is used, the pattern (<name> or <value>) is evaluated as a log-format string. This option cannot be used with the regex matching method. Finally, by default, the header value is considered as comma-separated list. Each part may be tested. The "full" option may be used to test the full header line. Note that matchings are case insensitive on the header names.
2020-05-05 08:47:36 +00:00
http-check set-var(check.hdr_value) str(x-test1)
MINOR: checks: Simplify matching on HTTP headers in HTTP expect rules Extra parameters on http-check expect rules, for the header matching method, to use log-format string or to match full header line have been removed. There is now separate matching methods to match a full header line or to match each comma-separated values. "http-check expect fhdr" must be used in the first case, and "http-check expect hdr" in the second one. In addition, to match log-format header name or value, "-lf" suffix must be added to "name" or "value" keyword. For intance: http-check expect hdr name "set-cookie" value-lf -m beg "sessid=%[var(check.cookie)]" Thanks to this changes, each parameter may only be interpreted in one way.
2020-05-05 18:23:13 +00:00
http-check expect hdr name -m beg "x-" value-lf -m str "%[var(check.hdr_value)]"
http-check expect fhdr name -m beg "x-" value-lf -m str "%[res.fhdr(x-hdr-name)]"
MEDIUM: checks: Support matching on headers for http-check expect rules It is now possible to add http-check expect rules matching HTTP header names and values. Here is the format of these rules: http-check expect header name [ -m <meth> ] <name> [log-format] \ [ value [ -m <meth> ] <value> [log-format] [full] ] the name pattern (name ...) is mandatory but the value pattern (value ...) is optionnal. If not specified, only the header presence is verified. <meth> is the matching method, applied on the header name or the header value. Supported matching methods are: * "str" (exact match) * "beg" (prefix match) * "end" (suffix match) * "sub" (substring match) * "reg" (regex match) If not specified, exact matching method is used. If the "log-format" option is used, the pattern (<name> or <value>) is evaluated as a log-format string. This option cannot be used with the regex matching method. Finally, by default, the header value is considered as comma-separated list. Each part may be tested. The "full" option may be used to test the full header line. Note that matchings are case insensitive on the header names.
2020-05-05 08:47:36 +00:00
server srv ${s1_addr}:${s1_port} check inter 100ms rise 1 fall 1
} -start
syslog S1 -wait