haproxy/reg-tests/http-messaging/scheme_based_normalize.vtc
Willy Tarreau f673923629 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 17:57:11 +01:00

126 lines
2.3 KiB
Plaintext

varnishtest "scheme based normalization (rfc3982 6.3.2)"
feature cmd "$HAPROXY_PROGRAM -cc 'version_atleast(2.5-dev0)'"
feature ignore_unknown_macro
syslog S1 -level info {
recv
expect ~ "^.* uri: GET http://hostname/ HTTP/2.0; host: {hostname}$"
recv
expect ~ "^.* uri: GET http://hostname:8080/ HTTP/2.0; host: {hostname:8080}$"
recv
expect ~ "^.* uri: GET https://hostname/ HTTP/2.0; host: {hostname}$"
recv
expect ~ "^.* uri: GET https://hostname:80/ HTTP/2.0; host: {hostname:80}$"
} -start
haproxy h1 -conf {
defaults
mode http
timeout connect "${HAPROXY_TEST_TIMEOUT-5s}"
timeout client "${HAPROXY_TEST_TIMEOUT-5s}"
timeout server "${HAPROXY_TEST_TIMEOUT-5s}"
frontend fe
bind "fd@${fe}" proto h2
http-request capture req.hdr(host) len 512
log-format "uri: %r; host: %hr"
log ${S1_addr}:${S1_port} len 2048 local0 debug err
http-request return status 200
} -start
# default port 80 with http scheme => should be normalized
client c1 -connect ${h1_fe_sock} {
txpri
stream 0 {
txsettings
rxsettings
txsettings -ack
rxsettings
expect settings.ack == true
} -run
stream 1 {
txreq \
-req "GET" \
-scheme "http" \
-url "/" \
-hdr ":authority" "hostname:80"
rxhdrs
expect resp.status == 200
} -run
} -run
# port 8080 with http scheme => no normalization
client c2 -connect ${h1_fe_sock} {
txpri
stream 0 {
txsettings
rxsettings
txsettings -ack
rxsettings
expect settings.ack == true
} -run
stream 1 {
txreq \
-req "GET" \
-scheme "http" \
-url "/" \
-hdr ":authority" "hostname:8080"
rxhdrs
expect resp.status == 200
} -run
} -run
# default port 443 with https scheme => should be normalized
client c3 -connect ${h1_fe_sock} {
txpri
stream 0 {
txsettings
rxsettings
txsettings -ack
rxsettings
expect settings.ack == true
} -run
stream 1 {
txreq \
-req "GET" \
-scheme "https" \
-url "/" \
-hdr ":authority" "hostname:443"
rxhdrs
expect resp.status == 200
} -run
} -run
# port 80 with https scheme => no normalization
client c4 -connect ${h1_fe_sock} {
txpri
stream 0 {
txsettings
rxsettings
txsettings -ack
rxsettings
expect settings.ack == true
} -run
stream 1 {
txreq \
-req "GET" \
-scheme "https" \
-url "/" \
-hdr ":authority" "hostname:80"
rxhdrs
expect resp.status == 200
} -run
} -run
syslog S1 -wait