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

138 lines
3.7 KiB
Plaintext
Raw Normal View History

MINOR: cache: Create res.cache_hit and res.cache_name sample fetches Res.cache_hit sample fetch returns a boolean which is true when the HTTP response was built out of a cache. The cache's name is returned by the res.cache_name sample_fetch. This resolves GitHub issue #900.
2020-10-27 10:55:57 +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"
MINOR: cache: Create res.cache_hit and res.cache_name sample fetches Res.cache_hit sample fetch returns a boolean which is true when the HTTP response was built out of a cache. The cache's name is returned by the res.cache_name sample_fetch. This resolves GitHub issue #900.
2020-10-27 10:55:57 +00:00
chunkedlen 15
chunkedlen 15
chunkedlen 15
chunkedlen 0
} -start
server s2 {
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"
MINOR: cache: Create res.cache_hit and res.cache_name sample fetches Res.cache_hit sample fetch returns a boolean which is true when the HTTP response was built out of a cache. The cache's name is returned by the res.cache_name sample_fetch. This resolves GitHub issue #900.
2020-10-27 10:55:57 +00:00
chunkedlen 16
chunkedlen 16
chunkedlen 16
chunkedlen 0
} -start
server s3 {
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"
MINOR: cache: Create res.cache_hit and res.cache_name sample fetches Res.cache_hit sample fetch returns a boolean which is true when the HTTP response was built out of a cache. The cache's name is returned by the res.cache_name sample_fetch. This resolves GitHub issue #900.
2020-10-27 10:55:57 +00:00
chunkedlen 17
chunkedlen 17
chunkedlen 17
chunkedlen 0
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"
MINOR: cache: Create res.cache_hit and res.cache_name sample fetches Res.cache_hit sample fetch returns a boolean which is true when the HTTP response was built out of a cache. The cache's name is returned by the res.cache_name sample_fetch. This resolves GitHub issue #900.
2020-10-27 10:55:57 +00:00
chunkedlen 17
chunkedlen 17
chunkedlen 17
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
MINOR: cache: Create res.cache_hit and res.cache_name sample fetches Res.cache_hit sample fetch returns a boolean which is true when the HTTP response was built out of a cache. The cache's name is returned by the res.cache_name sample_fetch. This resolves GitHub issue #900.
2020-10-27 10:55:57 +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}"
MINOR: cache: Create res.cache_hit and res.cache_name sample fetches Res.cache_hit sample fetch returns a boolean which is true when the HTTP response was built out of a cache. The cache's name is returned by the res.cache_name sample_fetch. This resolves GitHub issue #900.
2020-10-27 10:55:57 +00:00
frontend fe
bind "fd@${fe}"
use_backend first_be if { path_beg /first }
use_backend nocache_be if { path_beg /nocache }
default_backend second_be
backend first_be
http-request cache-use first_cache
server www ${s1_addr}:${s1_port}
http-response cache-store first_cache
http-response set-header X-Cache-Hit %[res.cache_hit]
http-response set-header X-Cache-Name %[res.cache_name]
backend second_be
http-request cache-use second_cache
server www ${s2_addr}:${s2_port}
http-response cache-store second_cache
http-response set-header X-Cache-Hit %[res.cache_hit]
http-response set-header X-Cache-Name %[res.cache_name]
backend nocache_be
server www ${s3_addr}:${s3_port}
http-response set-header X-Cache-Hit %[res.cache_hit]
http-response set-header X-Cache-Name %[res.cache_name]
cache first_cache
total-max-size 3
max-age 40
max-object-size 3000
cache second_cache
total-max-size 3
max-age 20
max-object-size 3072
} -start
client c1 -connect ${h1_fe_sock} {
txreq -url "/first"
rxresp
expect resp.status == 200
expect resp.bodylen == 45
expect resp.http.X-Cache-Hit == 0
expect resp.http.X-Cache-Name == ""
txreq -url "/second"
rxresp
expect resp.status == 200
expect resp.bodylen == 48
expect resp.http.X-Cache-Hit == 0
expect resp.http.X-Cache-Name == ""
txreq -url "/nocache"
rxresp
expect resp.status == 200
expect resp.bodylen == 51
expect resp.http.X-Cache-Hit == 0
expect resp.http.X-Cache-Name == ""
# Response should come form the cache now
txreq -url "/nocache"
rxresp
expect resp.status == 200
expect resp.bodylen == 51
expect resp.http.X-Cache-Hit == 0
expect resp.http.X-Cache-Name == ""
txreq -url "/first"
rxresp
expect resp.status == 200
expect resp.bodylen == 45
expect resp.http.X-Cache-Hit == 1
expect resp.http.X-Cache-Name == "first_cache"
txreq -url "/second"
rxresp
expect resp.status == 200
expect resp.bodylen == 48
expect resp.http.X-Cache-Hit == 1
expect resp.http.X-Cache-Name == "second_cache"
} -run