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/http-rules/acl_cli_spaces.vtc

79 lines
1.6 KiB
Plaintext
Raw Normal View History

REGTEST: http-rules: test spaces in ACLs with master CLI Do the tests for spaces on the CLI with the master CLI. Could be backported as far as 2.0 once the required patches are applied.
2020-06-18 16:56:44 +00:00
varnishtest "haproxy ACL, CLI and mCLI spaces"
REGTEST: http-rules: test spaces in ACLs This reg-test tests the spaces in an ACL file, it tries to add new entries with spaces from the CLI This reg-test could backported in all stable branches if the fix for spaces on the CLI was backported.
2020-06-18 16:52:18 +00:00
feature ignore_unknown_macro
server s1 {
rxreq
expect req.method == "GET"
txresp
} -repeat 2 -start
REGTEST: http-rules: test spaces in ACLs with master CLI Do the tests for spaces on the CLI with the master CLI. Could be backported as far as 2.0 once the required patches are applied.
2020-06-18 16:56:44 +00:00
haproxy h1 -W -S -conf {
REGTEST: http-rules: test spaces in ACLs This reg-test tests the spaces in an ACL file, it tries to add new entries with spaces from the CLI This reg-test could backported in all stable branches if the fix for spaces on the CLI was backported.
2020-06-18 16:52:18 +00:00
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 connect "${HAPROXY_TEST_TIMEOUT-5s}"
timeout client "${HAPROXY_TEST_TIMEOUT-5s}"
timeout server "${HAPROXY_TEST_TIMEOUT-5s}"
REGTEST: http-rules: test spaces in ACLs This reg-test tests the spaces in an ACL file, it tries to add new entries with spaces from the CLI This reg-test could backported in all stable branches if the fix for spaces on the CLI was backported.
2020-06-18 16:52:18 +00:00
frontend fe1
bind "fd@${fe1}"
http-request deny if { req.hdr(user-agent) -i -m str -f ${testdir}/agents.acl }
default_backend be1
backend be1
server s1 ${s1_addr}:${s1_port}
} -start
client c1 -connect ${h1_fe1_sock} {
txreq -hdr "User-Agent: Mon User Agent"
rxresp
expect resp.status == 200
} -run
haproxy h1 -cli {
REGTESTS: cli: add delay 0.1 before connect to cli When vtest starts haproxy process, it loops until the moment, when haproxy pidfile is created. When pidfile is created, vtest considers that haproxy process is ready and it starts to perform test commands, in particular, it connects to CLI. It's not very reliable approach to base the check of the process readiness on the PID file. After master-worker architecture refactoring pidfile is created in the early init stage, but master and worker are not yet finished its initialization routines. So, all mcli tests and some tests where we sent commands to CLI start to fail regularly. In vtest at the moment there is no any other approach to check that the process is really ready. So let's add a delay 0.1s before connecting to CLI in all mcli tests and in acl_cli_spaces test.
2024-10-16 16:27:30 +00:00
delay 0.1
REGTEST: http-rules: test spaces in ACLs This reg-test tests the spaces in an ACL file, it tries to add new entries with spaces from the CLI This reg-test could backported in all stable branches if the fix for spaces on the CLI was backported.
2020-06-18 16:52:18 +00:00
send "add acl ${testdir}/agents.acl Mon\\ User\\ Agent\\;"
expect ~ .*
send "show acl ${testdir}/agents.acl"
expect ~ ".*Mon User Agent.*"
}
client c1 -connect ${h1_fe1_sock} {
txreq -hdr "User-Agent: Mon User Agent;"
rxresp
expect resp.status == 403
} -run
REGTEST: http-rules: test spaces in ACLs with master CLI Do the tests for spaces on the CLI with the master CLI. Could be backported as far as 2.0 once the required patches are applied.
2020-06-18 16:56:44 +00:00
haproxy h1 -cli {
REGTESTS: cli: add delay 0.1 before connect to cli When vtest starts haproxy process, it loops until the moment, when haproxy pidfile is created. When pidfile is created, vtest considers that haproxy process is ready and it starts to perform test commands, in particular, it connects to CLI. It's not very reliable approach to base the check of the process readiness on the PID file. After master-worker architecture refactoring pidfile is created in the early init stage, but master and worker are not yet finished its initialization routines. So, all mcli tests and some tests where we sent commands to CLI start to fail regularly. In vtest at the moment there is no any other approach to check that the process is really ready. So let's add a delay 0.1s before connecting to CLI in all mcli tests and in acl_cli_spaces test.
2024-10-16 16:27:30 +00:00
delay 0.1
REGTEST: http-rules: test spaces in ACLs with master CLI Do the tests for spaces on the CLI with the master CLI. Could be backported as far as 2.0 once the required patches are applied.
2020-06-18 16:56:44 +00:00
send "del acl ${testdir}/agents.acl Mon\\ User\\ Agent\\;"
expect ~ .*
send "show acl ${testdir}/agents.acl"
expect ~ .*
}
client c1 -connect ${h1_fe1_sock} {
txreq -hdr "User-Agent: Mon User Agent;"
rxresp
expect resp.status == 200
} -run
# Try it with the master CLI
haproxy h1 -mcli {
REGTESTS: cli: add delay 0.1 before connect to cli When vtest starts haproxy process, it loops until the moment, when haproxy pidfile is created. When pidfile is created, vtest considers that haproxy process is ready and it starts to perform test commands, in particular, it connects to CLI. It's not very reliable approach to base the check of the process readiness on the PID file. After master-worker architecture refactoring pidfile is created in the early init stage, but master and worker are not yet finished its initialization routines. So, all mcli tests and some tests where we sent commands to CLI start to fail regularly. In vtest at the moment there is no any other approach to check that the process is really ready. So let's add a delay 0.1s before connecting to CLI in all mcli tests and in acl_cli_spaces test.
2024-10-16 16:27:30 +00:00
delay 0.1
REGTEST: http-rules: test spaces in ACLs with master CLI Do the tests for spaces on the CLI with the master CLI. Could be backported as far as 2.0 once the required patches are applied.
2020-06-18 16:56:44 +00:00
send "@1 add acl ${testdir}/agents.acl Mon\\ User\\ Agent\\;;@1 show acl ${testdir}/agents.acl"
expect ~ ".*Mon User Agent;.*"
}
client c1 -connect ${h1_fe1_sock} {
txreq -hdr "User-Agent: Mon User Agent;"
rxresp
expect resp.status == 403
} -run