If you have much gzip/gunzip activity, it may be an advantage to use workspace for these allocations to reduce malloc activity. Be aware that gzip needs 256+KB and gunzip needs 32+KB of workspace (64+KB if ESI processing).
gzip_window
...
...
@@ -219,7 +216,7 @@ http_gzip_support
- Default: on
- Flags: experimental
Enable gzip support. When enabled Varnish will compress uncompressed objects before they are stored in the cache. If a client does not support gzip encoding Varnish will uncompress compressed objects on demand. Varnish will also rewrite the Accept-Encoding header of clients indicating support for gzip to:
Enable gzip support. When enabled Varnish will compress uncompressed objects before they are stored in the cache. If a client does not support gzip encoding Varnish will uncompress compressed objects on demand. Varnish will also rewrite the Accept-Encoding header of clients indicating support for gzip to::
Accept-Encoding: gzip
...
...
@@ -241,7 +238,7 @@ http_range_support
http_req_hdr_len
- Units: bytes
- Default: 4096
- Default: 8192
Maximum length of any HTTP client request header we will allow. The limit is inclusive its continuation lines.
...
...
@@ -254,7 +251,7 @@ http_req_size
http_resp_hdr_len
- Units: bytes
- Default: 4096
- Default: 8192
Maximum length of any HTTP backend response header we will allow. The limit is inclusive its continuation lines.
...
...
@@ -314,7 +311,7 @@ max_restarts
nuke_limit
- Units: allocations
- Default: 10
- Default: 50
- Flags: experimental
Maximum number of objects we attempt to nuke in orderto make space for a object body.