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.1 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
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
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
timeout connect 1s
timeout client 1s
timeout server 1s
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: *"
rxresp
expect resp.status == 304
txreq \
-hdr "if-none-match: \"etag\""
rxresp
expect resp.status == 304
txreq \
-hdr "if-none-match: W/\"etag\""
rxresp
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\""
rxresp
expect resp.status == 304
} -run