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/basic.vtc

54 lines
1.0 KiB
Plaintext
Raw Normal View History

REGTEST: Add a basic test for the cache. The client makes the same HTTP request four times. The varnishtest HTTP server serves the first client request and quits. So, the three last requests are handled by the haproxy cache.
2018-11-28 10:36:48 +00:00
varnishtest "Basic cache test"
feature ignore_unknown_macro
server s1 {
rxreq
MEDIUM: cache: Change caching conditions Do not cache responses that do not have an explicit expiration time (s-maxage or max-age Cache-Control directives or Expires header) or a validator (ETag or Last-Modified headers) anymore, as suggested in RFC 7234#3. The TX_FLAG_IGNORE flag is used instead of the TX_FLAG_CACHEABLE so as not to change the behavior of the checkcache option.
2020-11-12 10:14:41 +00:00
txresp -nolen -hdr "Transfer-Encoding: chunked" \
-hdr "Cache-Control: max-age=5"
REGTEST: Add a basic test for the cache. The client makes the same HTTP request four times. The varnishtest HTTP server serves the first client request and quits. So, the three last requests are handled by the haproxy cache.
2018-11-28 10:36:48 +00:00
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 {
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: Add a basic test for the cache. The client makes the same HTTP request four times. The varnishtest HTTP server serves the first client request and quits. So, the three last requests are handled by the haproxy cache.
2018-11-28 10:36:48 +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
} -repeat 4 -run