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/cache/if-none-match.vtc

90 lines
2.2 KiB
Plaintext
Raw Normal View History

REGTEST: cache: Add if-none-match test case Test that if-none-match header is properly taken into account and that when the conditions are fulfilled, a "304 Not Modified" response can be sent to the client. Co-authored-by: Tim Duesterhus <tim@bastelstu.be>
2020-10-22 08:40:06 +00:00
varnishtest "If-None-Match support"
#REQUIRE_VERSION=2.3
feature ignore_unknown_macro
server s1 {
rxreq
txresp -nolen -hdr "Transfer-Encoding: chunked" \
-hdr "ETag: \"etag\""
chunkedlen 1
chunkedlen 1
chunkedlen 2
chunkedlen 3
chunkedlen 5
chunkedlen 8
chunkedlen 13
chunkedlen 21
chunkedlen 34
chunkedlen 55
chunkedlen 89
chunkedlen 144
chunkedlen 233
chunkedlen 0
} -start
REGTESTS: enable -dW on almost all tests to fail on warnings Now that warnings were almost all removed, let's enable zero-warning via -dW. All tests were adjusted, but two: - mcli/mcli_start_progs.vtc: the programs section currently cannot be silenced - stats/stats-file.vtc: the warning comes from the stats file itself on comment lines. All other ones are now OK.
2024-11-19 06:11:02 +00:00
haproxy h1 -arg '-dW' -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
REGTEST: cache: Add if-none-match test case Test that if-none-match header is properly taken into account and that when the conditions are fulfilled, a "304 Not Modified" response can be sent to the client. Co-authored-by: Tim Duesterhus <tim@bastelstu.be>
2020-10-22 08:40:06 +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: cache: Add if-none-match test case Test that if-none-match header is properly taken into account and that when the conditions are fulfilled, a "304 Not Modified" response can be sent to the client. Co-authored-by: Tim Duesterhus <tim@bastelstu.be>
2020-10-22 08:40:06 +00:00
frontend fe
bind "fd@${fe}"
default_backend test
backend test
http-request cache-use my_cache
server www ${s1_addr}:${s1_port}
http-response cache-store my_cache
cache my_cache
total-max-size 3
max-age 20
max-object-size 3072
} -start
client c1 -connect ${h1_fe_sock} {
txreq
rxresp
expect resp.status == 200
expect resp.bodylen == 609
txreq
rxresp
expect resp.status == 200
expect resp.bodylen == 609
txreq \
-hdr "if-none-match: *"
REGTESTS: cache: Use rxresphdrs to only get headers for 304 responses 304 responses contains "Content-length" or "Transfer-encoding" headers. rxresp action expects to get a payload in this case, even if 304 reponses must not have any payload. A workaround was added to remove these headers from the 304 responses. However, a better solution is to only get the response headers from clients using rxresphdrs action. If a payload is erroneously added in these reponses, the scripts will fail the same way. So it is safe.
2023-02-22 15:12:43 +00:00
rxresphdrs
REGTEST: cache: Add if-none-match test case Test that if-none-match header is properly taken into account and that when the conditions are fulfilled, a "304 Not Modified" response can be sent to the client. Co-authored-by: Tim Duesterhus <tim@bastelstu.be>
2020-10-22 08:40:06 +00:00
expect resp.status == 304
txreq \
-hdr "if-none-match: \"etag\""
REGTESTS: cache: Use rxresphdrs to only get headers for 304 responses 304 responses contains "Content-length" or "Transfer-encoding" headers. rxresp action expects to get a payload in this case, even if 304 reponses must not have any payload. A workaround was added to remove these headers from the 304 responses. However, a better solution is to only get the response headers from clients using rxresphdrs action. If a payload is erroneously added in these reponses, the scripts will fail the same way. So it is safe.
2023-02-22 15:12:43 +00:00
rxresphdrs
REGTEST: cache: Add if-none-match test case Test that if-none-match header is properly taken into account and that when the conditions are fulfilled, a "304 Not Modified" response can be sent to the client. Co-authored-by: Tim Duesterhus <tim@bastelstu.be>
2020-10-22 08:40:06 +00:00
expect resp.status == 304
txreq \
-hdr "if-none-match: W/\"etag\""
REGTESTS: cache: Use rxresphdrs to only get headers for 304 responses 304 responses contains "Content-length" or "Transfer-encoding" headers. rxresp action expects to get a payload in this case, even if 304 reponses must not have any payload. A workaround was added to remove these headers from the 304 responses. However, a better solution is to only get the response headers from clients using rxresphdrs action. If a payload is erroneously added in these reponses, the scripts will fail the same way. So it is safe.
2023-02-22 15:12:43 +00:00
rxresphdrs
REGTEST: cache: Add if-none-match test case Test that if-none-match header is properly taken into account and that when the conditions are fulfilled, a "304 Not Modified" response can be sent to the client. Co-authored-by: Tim Duesterhus <tim@bastelstu.be>
2020-10-22 08:40:06 +00:00
expect resp.status == 304
} -run
client c2 -connect ${h1_fe_sock} {
txreq \
-hdr "if-none-match: \"wrong_etag\""
rxresp
expect resp.status == 200
expect resp.bodylen == 609
txreq \
-hdr "if-none-match: W/\"wrong_etag\", W/\"etag\""
REGTESTS: cache: Use rxresphdrs to only get headers for 304 responses 304 responses contains "Content-length" or "Transfer-encoding" headers. rxresp action expects to get a payload in this case, even if 304 reponses must not have any payload. A workaround was added to remove these headers from the 304 responses. However, a better solution is to only get the response headers from clients using rxresphdrs action. If a payload is erroneously added in these reponses, the scripts will fail the same way. So it is safe.
2023-02-22 15:12:43 +00:00
rxresphdrs
REGTEST: cache: Add if-none-match test case Test that if-none-match header is properly taken into account and that when the conditions are fulfilled, a "304 Not Modified" response can be sent to the client. Co-authored-by: Tim Duesterhus <tim@bastelstu.be>
2020-10-22 08:40:06 +00:00
expect resp.status == 304
} -run