diff options
| author | David Kalnischkies <david@kalnischkies.de> | 2021-09-16 19:48:33 +0200 |
|---|---|---|
| committer | David Kalnischkies <david@kalnischkies.de> | 2021-09-16 22:40:00 +0200 |
| commit | d013f8957c0d464e0059cc107ca79d887cf9f8aa (patch) | |
| tree | 7324a6308bdbc1034cba26459c2204111b7f7510 /test | |
| parent | 61c1d7d3658fdcd4b32f8b071cef7941120f8abc (diff) | |
Disable HTTP Range usage if varnish < 6.4 is involved
Debian buster (oldstable) ships 6.1 while bullseye (stable) ships 6.5
and so the later is 'fixed'. Upstream declares 6.0 still as supported.
It might be still a while we encounter "bad" versions in the wild, so
if we can detect and work around the issue at runtime automatically we
can save some users from running into "persistent" partial files.
References: https://varnish-cache.org/docs/6.4/whats-new/changes-6.4.html#changes-in-behavior
Diffstat (limited to 'test')
| -rwxr-xr-x | test/integration/test-http-if-range | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/test/integration/test-http-if-range b/test/integration/test-http-if-range index 7eb667ba7..ca9f3b2e6 100755 --- a/test/integration/test-http-if-range +++ b/test/integration/test-http-if-range @@ -75,3 +75,8 @@ testrun 'buggy server' '200' '206' '206' '416' echo 'Acquire::http::localhost::AllowRanges "false";' > rootdir/etc/apt/apt.conf.d/noallowranges testrun 'range disabled by conf' '200' '200' '200' '200' rm rootdir/etc/apt/apt.conf.d/noallowranges +# detect varnish < 6.4 automatically +webserverconfig 'aptwebserver::response-header::Via' '1.1 varnish (Varnish/6.1)' +testrun 'bad varnish' '200' '200' '200' '200' +webserverconfig 'aptwebserver::response-header::Via' '1.1 varnish (Varnish/6.4)' +testrun 'good varnish' '200' '206' '206' '416' |