haproxy/reg-tests/http-messaging/http_bodyless_response.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

128 lines
3.1 KiB
Plaintext

varnishtest "A test to be sure payload is skipped for bodyless responses"
feature ignore_unknown_macro
#REQUIRE_VERSION=2.4
server s1 {
rxreq
txresp \
-status 200 \
-body "skipped data"
rxreq
txresp \
-status 200 \
-bodylen 20000
rxreq
txresp \
-status 200 \
-nolen -hdr "Transfer-Encoding: chunked"
chunkedlen 15
chunkedlen 1024
chunkedlen 4048
chunkedlen 0
rxreq
txresp \
-status 200 \
-body "last response"
} -repeat 2 -start
haproxy h1 -conf {
global
# WT: limit false-positives causing "HTTP header incomplete" due to
# idle server connections being randomly used and randomly expiring
# under us.
tune.idle-pool.shared off
defaults
mode http
timeout connect "${HAPROXY_TEST_TIMEOUT-5s}"
timeout client "${HAPROXY_TEST_TIMEOUT-5s}"
timeout server "${HAPROXY_TEST_TIMEOUT-5s}"
listen fe1
bind "fd@${fe1}"
# Rewrite the method to be sure to get the response payload
# on the server side
http-request set-method GET
server s1 ${s1_addr}:${s1_port}
listen int
bind "fd@${int}" proto h2
# Rewrite the method to be sure to get the response payload
# on the server side
http-request set-method GET
server s1 ${s1_addr}:${s1_port}
#server s1 ${h1_fe1_addr}:${h1_fe1_port}
listen fe2
bind "fd@${fe2}"
server s1 ${h1_int_addr}:${h1_int_port} proto h2
} -start
client c1 -connect ${h1_fe1_sock} {
txreq \
-req "HEAD" \
-url "/req1"
rxresp
expect resp.status == 200
expect resp.body == ""
txreq \
-req "HEAD" \
-url "/req2"
rxresp
expect resp.status == 200
expect resp.body == ""
txreq \
-req "HEAD" \
-url "/req3"
rxresp
expect resp.status == 200
expect resp.body == ""
# The last one have a body and validate the connection was not closed
# unexpectedly and no payload was received for previous requests
txreq \
-req "GET" \
-url "/req4"
rxresp
expect resp.status == 200
expect resp.body == "last response"
} -run
client c2 -connect ${h1_fe2_sock} {
txreq \
-req "HEAD" \
-url "/req1"
rxresp
expect resp.status == 200
expect resp.body == ""
txreq \
-req "HEAD" \
-url "/req2"
rxresp
expect resp.status == 200
expect resp.body == ""
txreq \
-req "HEAD" \
-url "/req3"
rxresp
expect resp.status == 200
expect resp.body == ""
# The last one have a body and validate the connection was not closed
# unexpectedly and no payload was received for previous requests
txreq \
-req "GET" \
-url "/req4"
rxresp
expect resp.status == 200
expect resp.body == "last response"
} -run