Varnish cache behaves weirdly on chunked transfers #7

New Issue

caskd · 2020-03-17T22:12:09Z

caskd commented

2020-03-17 22:12:09 +00:00

Varnish caches chunked transfers in a weird, rather wrong way ending up in problems while streaming videos or seeking through them. The range header seems to not be the problem as hashing that does not help against the problem. This was tested further in the chain and the following processor (HAProxy) does not have the problem, so this is Varnish for sure.

Varnish caches chunked transfers in a weird, rather wrong way ending up in problems while streaming videos or seeking through them. The `range` header seems to not be the problem as hashing that does not help against the problem. This was tested further in the chain and the following processor (HAProxy) does not have the problem, so this is Varnish for sure.

caskd commented

2020-03-27 20:06:21 +00:00

Multiple ranges: https://github.com/varnishcache/varnish-cache/issues/2739

7d59c25676 shows that bypassing the cache while the Range header is present helps.

Multiple ranges: https://github.com/varnishcache/varnish-cache/issues/2739 https://git.redxen.eu/RedXen/frontend/commit/7d59c25676a220efe983d225d07b278423f25a2e shows that bypassing the cache while the `Range` header is present helps.

caskd commented

2020-04-25 15:45:00 +00:00

Resolved in 7d59c25676

Resolved in https://git.redxen.eu/RedXen/frontend-docker/commit/7d59c25676a220efe983d225d07b278423f25a2e

caskd closed this issue

2020-04-25 15:45:03 +00:00

This repo is archived. You cannot comment on issues.