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-errorfiles/http_errors.vtc

133 lines
3.9 KiB
Plaintext
Raw Normal View History

REGEST: Add reg tests about error files 2 reg tests are added. The first one ensures the declaration of errors in a proxy is fonctionnal. It declares http-errors sections and declare error files using the errorfile and the errorfiles directives, both in the default section and the frontend sections. The second one ensures it is possible to use a custom error file for an HTTP deny rule.
2020-01-20 12:49:48 +00:00
varnishtest "Test the errorfiles directive"
# This config tests the errorfiles directive.
feature ignore_unknown_macro
haproxy h1 -conf {
http-errors errors-1
errorfile 400 ${testdir}/errors/400-1.http
errorfile 403 ${testdir}/errors/403-1.http
errorfile 404 ${testdir}/errors/404-1.http
errorfile 500 ${testdir}/errors/500-1.http
http-errors errors-2
errorfile 400 ${testdir}/errors/400-2.http
errorfile 403 ${testdir}/errors/403-2.http
errorfile 404 ${testdir}/errors/404-2.http
http-errors errors-3
errorfile 400 ${testdir}/errors/400-3.http
errorfile 404 ${testdir}/errors/404-3.http
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}"
REGEST: Add reg tests about error files 2 reg tests are added. The first one ensures the declaration of errors in a proxy is fonctionnal. It declares http-errors sections and declare error files using the errorfile and the errorfiles directives, both in the default section and the frontend sections. The second one ensures it is possible to use a custom error file for an HTTP deny rule.
2020-01-20 12:49:48 +00:00
errorfiles errors-2
errorfile 400 ${testdir}/errors/400.http
errorfile 404 ${testdir}/errors/404.http
frontend fe1
bind "fd@${fe1}"
http-request deny deny_status 400 if { path /400 }
BUG/MINOR: http-rules: Fix ACLs parsing for http deny rules The parsing of http deny rules with no argument or only the deny_status argument is buggy if followed by an ACLs expression (starting with "if" or "unless" keyword). Instead of using the proxy errorfiles, a dummy error is used. To fix the bug, the parsing function must also check for "if" or "unless" keyword in such cases. This patch should fix the issue #720. No backport is needed.
2020-06-30 07:32:01 +00:00
http-request deny if { path /403 }
REGEST: Add reg tests about error files 2 reg tests are added. The first one ensures the declaration of errors in a proxy is fonctionnal. It declares http-errors sections and declare error files using the errorfile and the errorfiles directives, both in the default section and the frontend sections. The second one ensures it is possible to use a custom error file for an HTTP deny rule.
2020-01-20 12:49:48 +00:00
http-request deny deny_status 404 if { path /404 }
http-request deny deny_status 500 if { path /500 }
frontend fe2
bind "fd@${fe2}"
errorfiles errors-1
errorfile 500 ${testdir}/errors/500.http
http-request deny deny_status 400 if { path /400 }
BUG/MINOR: http-rules: Fix ACLs parsing for http deny rules The parsing of http deny rules with no argument or only the deny_status argument is buggy if followed by an ACLs expression (starting with "if" or "unless" keyword). Instead of using the proxy errorfiles, a dummy error is used. To fix the bug, the parsing function must also check for "if" or "unless" keyword in such cases. This patch should fix the issue #720. No backport is needed.
2020-06-30 07:32:01 +00:00
http-request deny if { path /403 }
REGEST: Add reg tests about error files 2 reg tests are added. The first one ensures the declaration of errors in a proxy is fonctionnal. It declares http-errors sections and declare error files using the errorfile and the errorfiles directives, both in the default section and the frontend sections. The second one ensures it is possible to use a custom error file for an HTTP deny rule.
2020-01-20 12:49:48 +00:00
http-request deny deny_status 404 if { path /404 }
http-request deny deny_status 500 if { path /500 }
frontend fe3
bind "fd@${fe3}"
errorfile 500 ${testdir}/errors/500.http
errorfiles errors-1 500
errorfiles errors-3 400
http-request deny deny_status 400 if { path /400 }
BUG/MINOR: http-rules: Fix ACLs parsing for http deny rules The parsing of http deny rules with no argument or only the deny_status argument is buggy if followed by an ACLs expression (starting with "if" or "unless" keyword). Instead of using the proxy errorfiles, a dummy error is used. To fix the bug, the parsing function must also check for "if" or "unless" keyword in such cases. This patch should fix the issue #720. No backport is needed.
2020-06-30 07:32:01 +00:00
http-request deny if { path /403 }
REGEST: Add reg tests about error files 2 reg tests are added. The first one ensures the declaration of errors in a proxy is fonctionnal. It declares http-errors sections and declare error files using the errorfile and the errorfiles directives, both in the default section and the frontend sections. The second one ensures it is possible to use a custom error file for an HTTP deny rule.
2020-01-20 12:49:48 +00:00
http-request deny deny_status 404 if { path /404 }
http-request deny deny_status 500 if { path /500 }
} -start
client c1r1 -connect ${h1_fe1_sock} {
txreq -req GET -url /400
rxresp
expect resp.status == 400
expect resp.http.x-err-type == "default"
} -run
client c1r2 -connect ${h1_fe1_sock} {
txreq -req GET -url /403
rxresp
expect resp.status == 403
expect resp.http.x-err-type == "errors-2"
} -run
client c1r3 -connect ${h1_fe1_sock} {
txreq -req GET -url /404
rxresp
expect resp.status == 404
expect resp.http.x-err-type == "default"
} -run
client c1r4 -connect ${h1_fe1_sock} {
txreq -req GET -url /500
rxresp
expect resp.status == 500
expect resp.http.x-err-type == <undef>
} -run
client c2r1 -connect ${h1_fe2_sock} {
txreq -req GET -url /400
rxresp
expect resp.status == 400
expect resp.http.x-err-type == "errors-1"
} -run
client c2r2 -connect ${h1_fe2_sock} {
txreq -req GET -url /403
rxresp
expect resp.status == 403
expect resp.http.x-err-type == "errors-1"
} -run
client c2r3 -connect ${h1_fe2_sock} {
txreq -req GET -url /404
rxresp
expect resp.status == 404
expect resp.http.x-err-type == "errors-1"
} -run
client c2r4 -connect ${h1_fe2_sock} {
txreq -req GET -url /500
rxresp
expect resp.status == 500
expect resp.http.x-err-type == "default"
} -run
client c3r1 -connect ${h1_fe3_sock} {
txreq -req GET -url /400
rxresp
expect resp.status == 400
expect resp.http.x-err-type == "errors-3"
} -run
client c3r2 -connect ${h1_fe3_sock} {
txreq -req GET -url /403
rxresp
expect resp.status == 403
expect resp.http.x-err-type == "errors-2"
} -run
client c3r3 -connect ${h1_fe3_sock} {
txreq -req GET -url /404
rxresp
expect resp.status == 404
expect resp.http.x-err-type == "default"
} -run
client c3r4 -connect ${h1_fe3_sock} {
txreq -req GET -url /500
rxresp
expect resp.status == 500
expect resp.http.x-err-type == "errors-1"
} -run