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-messaging/http_bodyless_response.vtc

128 lines
3.1 KiB
Plaintext
Raw Normal View History

REGTESTS: Add a script to test payload skipping for bodyless HTTP responses This script is used to be sure unexpected payload in bodyless HTTP responses is properly ignored on outgoing side, both by H1 and H2 muxes.
2021-02-10 09:20:26 +00:00
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 {
REGTESTS: disable inter-thread idle connection sharing on sensitive tests Some regtests involve multiple requests from multiple clients, which can be dispatched as multiple requests to a server. It turns out that the idle connection sharing works so well that very quickly few connections are used, and regularly some of the remaining idle server connections time out at the moment they were going to be reused, causing those random "HTTP header incomplete" traces in the logs that make them fail often. In the end this is only an artefact of the test environment. And indeed, some tests like normalize-uri which perform a lot of reuse fail very often, about 20-30% of the times in the CI, and 100% of the time in local when running 1000 tests in a row. Others like ubase64, sample_fetches or vary_* fail less often but still a lot in tests. This patch addresses this by adding "tune.idle-pool.shared off" to all tests which have at least twice as many requests as clients. It proves very effective as no single error happens on normalize-uri anymore after 10000 tests. Also 100 full runs of all tests yield no error anymore. One test is tricky, http_abortonclose, it used to fail ~10 times per 1000 runs and with this workaround still fails once every 1000 runs. But the test is complex and there's a warning in it mentioning a possible issue when run in parallel due to a port reuse.
2021-05-09 12:41:41 +00:00
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
REGTESTS: Add a script to test payload skipping for bodyless HTTP responses This script is used to be sure unexpected payload in bodyless HTTP responses is properly ignored on outgoing side, both by H1 and H2 muxes.
2021-02-10 09:20:26 +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}"
REGTESTS: Add a script to test payload skipping for bodyless HTTP responses This script is used to be sure unexpected payload in bodyless HTTP responses is properly ignored on outgoing side, both by H1 and H2 muxes.
2021-02-10 09:20:26 +00:00
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