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-send.vtc

169 lines
4.5 KiB
Plaintext
Raw Normal View History

MINOR: checks: Add a way to send custom headers and payload during http chekcs The 'http-check send' directive have been added to add headers and optionnaly a payload to the request sent during HTTP healthchecks. The request line may be customized by the "option httpchk" directive but there was not official way to add extra headers. An old trick consisted to hide these headers at the end of the version string, on the "option httpchk" line. And it was impossible to add an extra payload with an "http-check expect" directive because of the "Connection: close" header appended to the request (See issue #16 for details). So to make things official and fully support payload additions, the "http-check send" directive have been added : option httpchk POST /status HTTP/1.1 http-check send hdr Content-Type "application/json;charset=UTF-8" \ hdr X-test-1 value1 hdr X-test-2 value2 \ body "{id: 1, field: \"value\"}" When a payload is defined, the Content-Length header is automatically added. So chunk-encoded requests are not supported yet. For now, there is no special validity checks on the extra headers. This patch is inspired by Kiran Gavali's work. It should fix the issue #16 and as far as possible, it may be backported, at least as far as 1.8.
2020-04-09 06:44:06 +00:00
varnishtest "Health-checks: http-check send test"
REGTEST: Add scripts to test based tcp-check health-checks These scripts have been added to validate the health-checks based on tcp-check rules (http, redis, MySQL...).
2020-04-22 13:16:58 +00:00
#REGTEST_TYPE=slow
REGTESTS: mark http-check-send.vtc as 2.4-only Since commit 39ff8c519 ("REGTESTS: complete http-check test"), it breaks on pre-2.4, let's update the required version.
2021-02-04 17:06:13 +00:00
#REQUIRE_VERSION=2.4
MINOR: checks: Add a way to send custom headers and payload during http chekcs The 'http-check send' directive have been added to add headers and optionnaly a payload to the request sent during HTTP healthchecks. The request line may be customized by the "option httpchk" directive but there was not official way to add extra headers. An old trick consisted to hide these headers at the end of the version string, on the "option httpchk" line. And it was impossible to add an extra payload with an "http-check expect" directive because of the "Connection: close" header appended to the request (See issue #16 for details). So to make things official and fully support payload additions, the "http-check send" directive have been added : option httpchk POST /status HTTP/1.1 http-check send hdr Content-Type "application/json;charset=UTF-8" \ hdr X-test-1 value1 hdr X-test-2 value2 \ body "{id: 1, field: \"value\"}" When a payload is defined, the Content-Length header is automatically added. So chunk-encoded requests are not supported yet. For now, there is no special validity checks on the extra headers. This patch is inspired by Kiran Gavali's work. It should fix the issue #16 and as far as possible, it may be backported, at least as far as 1.8.
2020-04-09 06:44:06 +00:00
feature ignore_unknown_macro
# This script tests HTTP health-checks and more particularly the "http-check
# send" directive.
server s1 {
rxreq
expect req.method == OPTIONS
expect req.url == /
expect req.proto == HTTP/1.0
txresp
} -start
server s2 {
rxreq
expect req.method == GET
expect req.url == /test
expect req.proto == HTTP/1.1
REGTESTS: unbreak http-check-send.vtc As noticed by Christopher, I messed up the version fix in commit cb4ed02ef ("REGTESTS: mark http-check-send.vtc as 2.4-only"), as while looking up the commit introducing the change I accidently reverted it. Let's reinsert the contents of the file prior to that fix, except the version, of course.
2021-02-05 09:13:15 +00:00
expect req.http.connection == "close"
MINOR: checks: Add a way to send custom headers and payload during http chekcs The 'http-check send' directive have been added to add headers and optionnaly a payload to the request sent during HTTP healthchecks. The request line may be customized by the "option httpchk" directive but there was not official way to add extra headers. An old trick consisted to hide these headers at the end of the version string, on the "option httpchk" line. And it was impossible to add an extra payload with an "http-check expect" directive because of the "Connection: close" header appended to the request (See issue #16 for details). So to make things official and fully support payload additions, the "http-check send" directive have been added : option httpchk POST /status HTTP/1.1 http-check send hdr Content-Type "application/json;charset=UTF-8" \ hdr X-test-1 value1 hdr X-test-2 value2 \ body "{id: 1, field: \"value\"}" When a payload is defined, the Content-Length header is automatically added. So chunk-encoded requests are not supported yet. For now, there is no special validity checks on the extra headers. This patch is inspired by Kiran Gavali's work. It should fix the issue #16 and as far as possible, it may be backported, at least as far as 1.8.
2020-04-09 06:44:06 +00:00
txresp
} -start
server s3 {
rxreq
expect req.method == OPTIONS
expect req.url == /
expect req.proto == HTTP/1.0
expect req.http.hdr == <undef>
expect req.http.host == <undef>
expect req.http.x-test == <undef>
expect req.bodylen == 0
txresp
} -start
server s4 {
rxreq
expect req.method == GET
expect req.url == /status
expect req.proto == HTTP/1.1
REGTESTS: unbreak http-check-send.vtc As noticed by Christopher, I messed up the version fix in commit cb4ed02ef ("REGTESTS: mark http-check-send.vtc as 2.4-only"), as while looking up the commit introducing the change I accidently reverted it. Let's reinsert the contents of the file prior to that fix, except the version, of course.
2021-02-05 09:13:15 +00:00
expect req.http.connection == "close"
MINOR: checks: Add a way to send custom headers and payload during http chekcs The 'http-check send' directive have been added to add headers and optionnaly a payload to the request sent during HTTP healthchecks. The request line may be customized by the "option httpchk" directive but there was not official way to add extra headers. An old trick consisted to hide these headers at the end of the version string, on the "option httpchk" line. And it was impossible to add an extra payload with an "http-check expect" directive because of the "Connection: close" header appended to the request (See issue #16 for details). So to make things official and fully support payload additions, the "http-check send" directive have been added : option httpchk POST /status HTTP/1.1 http-check send hdr Content-Type "application/json;charset=UTF-8" \ hdr X-test-1 value1 hdr X-test-2 value2 \ body "{id: 1, field: \"value\"}" When a payload is defined, the Content-Length header is automatically added. So chunk-encoded requests are not supported yet. For now, there is no special validity checks on the extra headers. This patch is inspired by Kiran Gavali's work. It should fix the issue #16 and as far as possible, it may be backported, at least as far as 1.8.
2020-04-09 06:44:06 +00:00
expect req.http.hdr == <undef>
expect req.http.host == "my-www-host"
expect req.http.x-test == true
expect req.http.content-length == 4
expect req.bodylen == 4
expect req.body == "test"
txresp
} -start
server s5 {
rxreq
REGTEST: Fix reg-tests about health-checks to adapt them to recent changes
2020-04-20 12:59:20 +00:00
expect req.method == OPTIONS
expect req.url == /
expect req.proto == HTTP/1.0
MINOR: checks: Add a way to send custom headers and payload during http chekcs The 'http-check send' directive have been added to add headers and optionnaly a payload to the request sent during HTTP healthchecks. The request line may be customized by the "option httpchk" directive but there was not official way to add extra headers. An old trick consisted to hide these headers at the end of the version string, on the "option httpchk" line. And it was impossible to add an extra payload with an "http-check expect" directive because of the "Connection: close" header appended to the request (See issue #16 for details). So to make things official and fully support payload additions, the "http-check send" directive have been added : option httpchk POST /status HTTP/1.1 http-check send hdr Content-Type "application/json;charset=UTF-8" \ hdr X-test-1 value1 hdr X-test-2 value2 \ body "{id: 1, field: \"value\"}" When a payload is defined, the Content-Length header is automatically added. So chunk-encoded requests are not supported yet. For now, there is no special validity checks on the extra headers. This patch is inspired by Kiran Gavali's work. It should fix the issue #16 and as far as possible, it may be backported, at least as far as 1.8.
2020-04-09 06:44:06 +00:00
expect req.http.hdr == <undef>
expect req.http.host == "other-www-host"
expect req.http.x-test == <undef>
expect req.http.x-new-test == true
expect req.http.content-length == 10
expect req.bodylen == 10
expect req.body == "other test"
txresp
} -start
REGTESTS: unbreak http-check-send.vtc As noticed by Christopher, I messed up the version fix in commit cb4ed02ef ("REGTESTS: mark http-check-send.vtc as 2.4-only"), as while looking up the commit introducing the change I accidently reverted it. Let's reinsert the contents of the file prior to that fix, except the version, of course.
2021-02-05 09:13:15 +00:00
server s6 {
rxreq
expect req.method == GET
expect req.url == /
expect req.proto == HTTP/1.1
expect req.http.host == "ws-host"
expect req.http.connection == "upgrade"
expect req.http.upgrade == "raw-proto"
txresp \
-status 101 \
-hdr "connection: upgrade" \
-hdr "upgrade: raw-proto"
} -start
MINOR: checks: Add a way to send custom headers and payload during http chekcs The 'http-check send' directive have been added to add headers and optionnaly a payload to the request sent during HTTP healthchecks. The request line may be customized by the "option httpchk" directive but there was not official way to add extra headers. An old trick consisted to hide these headers at the end of the version string, on the "option httpchk" line. And it was impossible to add an extra payload with an "http-check expect" directive because of the "Connection: close" header appended to the request (See issue #16 for details). So to make things official and fully support payload additions, the "http-check send" directive have been added : option httpchk POST /status HTTP/1.1 http-check send hdr Content-Type "application/json;charset=UTF-8" \ hdr X-test-1 value1 hdr X-test-2 value2 \ body "{id: 1, field: \"value\"}" When a payload is defined, the Content-Length header is automatically added. So chunk-encoded requests are not supported yet. For now, there is no special validity checks on the extra headers. This patch is inspired by Kiran Gavali's work. It should fix the issue #16 and as far as possible, it may be backported, at least as far as 1.8.
2020-04-09 06:44:06 +00:00
syslog S1 -level notice {
recv
expect ~ "[^:\\[ ]\\[${h1_pid}\\]: Health check for server be1/srv succeeded.*code: 200"
} -start
syslog S2 -level notice {
recv
expect ~ "[^:\\[ ]\\[${h1_pid}\\]: Health check for server be2/srv succeeded.*code: 200"
} -start
syslog S3 -level notice {
recv
expect ~ "[^:\\[ ]\\[${h1_pid}\\]: Health check for server be3/srv succeeded.*code: 200"
} -start
syslog S4 -level notice {
recv
expect ~ "[^:\\[ ]\\[${h1_pid}\\]: Health check for server be4/srv succeeded.*code: 200"
} -start
syslog S5 -level notice {
recv
expect ~ "[^:\\[ ]\\[${h1_pid}\\]: Health check for server be5/srv succeeded.*code: 200"
} -start
REGTESTS: unbreak http-check-send.vtc As noticed by Christopher, I messed up the version fix in commit cb4ed02ef ("REGTESTS: mark http-check-send.vtc as 2.4-only"), as while looking up the commit introducing the change I accidently reverted it. Let's reinsert the contents of the file prior to that fix, except the version, of course.
2021-02-05 09:13:15 +00:00
syslog S6 -level notice {
recv
expect ~ "[^:\\[ ]\\[${h1_pid}\\]: Health check for server be6_ws/srv succeeded.*code: 101"
} -start
MINOR: checks: Add a way to send custom headers and payload during http chekcs The 'http-check send' directive have been added to add headers and optionnaly a payload to the request sent during HTTP healthchecks. The request line may be customized by the "option httpchk" directive but there was not official way to add extra headers. An old trick consisted to hide these headers at the end of the version string, on the "option httpchk" line. And it was impossible to add an extra payload with an "http-check expect" directive because of the "Connection: close" header appended to the request (See issue #16 for details). So to make things official and fully support payload additions, the "http-check send" directive have been added : option httpchk POST /status HTTP/1.1 http-check send hdr Content-Type "application/json;charset=UTF-8" \ hdr X-test-1 value1 hdr X-test-2 value2 \ body "{id: 1, field: \"value\"}" When a payload is defined, the Content-Length header is automatically added. So chunk-encoded requests are not supported yet. For now, there is no special validity checks on the extra headers. This patch is inspired by Kiran Gavali's work. It should fix the issue #16 and as far as possible, it may be backported, at least as far as 1.8.
2020-04-09 06:44:06 +00:00
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}"
MINOR: checks: Add a way to send custom headers and payload during http chekcs The 'http-check send' directive have been added to add headers and optionnaly a payload to the request sent during HTTP healthchecks. The request line may be customized by the "option httpchk" directive but there was not official way to add extra headers. An old trick consisted to hide these headers at the end of the version string, on the "option httpchk" line. And it was impossible to add an extra payload with an "http-check expect" directive because of the "Connection: close" header appended to the request (See issue #16 for details). So to make things official and fully support payload additions, the "http-check send" directive have been added : option httpchk POST /status HTTP/1.1 http-check send hdr Content-Type "application/json;charset=UTF-8" \ hdr X-test-1 value1 hdr X-test-2 value2 \ body "{id: 1, field: \"value\"}" When a payload is defined, the Content-Length header is automatically added. So chunk-encoded requests are not supported yet. For now, there is no special validity checks on the extra headers. This patch is inspired by Kiran Gavali's work. It should fix the issue #16 and as far as possible, it may be backported, at least as far as 1.8.
2020-04-09 06:44:06 +00:00
option httpchk
option log-health-checks
backend be1
log ${S1_addr}:${S1_port} len 2048 local0
server srv ${s1_addr}:${s1_port} check inter 200ms rise 1 fall 1
backend be2
log ${S2_addr}:${S2_port} len 2048 local0
option httpchk GET /test HTTP/1.1
server srv ${s2_addr}:${s2_port} check inter 200ms rise 1 fall 1
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}"
MINOR: checks: Add a way to send custom headers and payload during http chekcs The 'http-check send' directive have been added to add headers and optionnaly a payload to the request sent during HTTP healthchecks. The request line may be customized by the "option httpchk" directive but there was not official way to add extra headers. An old trick consisted to hide these headers at the end of the version string, on the "option httpchk" line. And it was impossible to add an extra payload with an "http-check expect" directive because of the "Connection: close" header appended to the request (See issue #16 for details). So to make things official and fully support payload additions, the "http-check send" directive have been added : option httpchk POST /status HTTP/1.1 http-check send hdr Content-Type "application/json;charset=UTF-8" \ hdr X-test-1 value1 hdr X-test-2 value2 \ body "{id: 1, field: \"value\"}" When a payload is defined, the Content-Length header is automatically added. So chunk-encoded requests are not supported yet. For now, there is no special validity checks on the extra headers. This patch is inspired by Kiran Gavali's work. It should fix the issue #16 and as far as possible, it may be backported, at least as far as 1.8.
2020-04-09 06:44:06 +00:00
option httpchk GET /status HTTP/1.1\r\nHdr:\ must-be-removed
option log-health-checks
http-check send hdr Host "my-www-host" hdr X-test true body "test"
backend be3
option httpchk
log ${S3_addr}:${S3_port} len 2048 local0
server srv ${s3_addr}:${s3_port} check inter 200ms rise 1 fall 1
backend be4
log ${S4_addr}:${S4_port} len 2048 local0
server srv ${s4_addr}:${s4_port} check inter 200ms rise 1 fall 1
backend be5
log ${S5_addr}:${S5_port} len 2058 local0
http-check send hdr Host "other-www-host" hdr X-New-Test true body "other test"
server srv ${s5_addr}:${s5_port} check inter 200ms rise 1 fall 1
REGTESTS: unbreak http-check-send.vtc As noticed by Christopher, I messed up the version fix in commit cb4ed02ef ("REGTESTS: mark http-check-send.vtc as 2.4-only"), as while looking up the commit introducing the change I accidently reverted it. Let's reinsert the contents of the file prior to that fix, except the version, of course.
2021-02-05 09:13:15 +00:00
backend be6_ws
log ${S6_addr}:${S6_port} len 2048 local0
http-check send meth GET uri / ver HTTP/1.1 hdr host ws-host hdr connection upgrade hdr upgrade raw-proto
http-check expect status 101
server srv ${s6_addr}:${s6_port} check inter 200ms rise 1 fall 1
MINOR: checks: Add a way to send custom headers and payload during http chekcs The 'http-check send' directive have been added to add headers and optionnaly a payload to the request sent during HTTP healthchecks. The request line may be customized by the "option httpchk" directive but there was not official way to add extra headers. An old trick consisted to hide these headers at the end of the version string, on the "option httpchk" line. And it was impossible to add an extra payload with an "http-check expect" directive because of the "Connection: close" header appended to the request (See issue #16 for details). So to make things official and fully support payload additions, the "http-check send" directive have been added : option httpchk POST /status HTTP/1.1 http-check send hdr Content-Type "application/json;charset=UTF-8" \ hdr X-test-1 value1 hdr X-test-2 value2 \ body "{id: 1, field: \"value\"}" When a payload is defined, the Content-Length header is automatically added. So chunk-encoded requests are not supported yet. For now, there is no special validity checks on the extra headers. This patch is inspired by Kiran Gavali's work. It should fix the issue #16 and as far as possible, it may be backported, at least as far as 1.8.
2020-04-09 06:44:06 +00:00
} -start
syslog S1 -wait
syslog S2 -wait
syslog S3 -wait
syslog S4 -wait
syslog S5 -wait
REGTESTS: unbreak http-check-send.vtc As noticed by Christopher, I messed up the version fix in commit cb4ed02ef ("REGTESTS: mark http-check-send.vtc as 2.4-only"), as while looking up the commit introducing the change I accidently reverted it. Let's reinsert the contents of the file prior to that fix, except the version, of course.
2021-02-05 09:13:15 +00:00
syslog S6 -wait