[master] ac3111510 docs: clarify that A-E header needs to be set on bereq.http for pass requests
Nils Goroll
nils.goroll at uplex.de
Sun Feb 9 15:12:05 UTC 2025
commit ac3111510a29564ae2761e9a49c0fac7e5df69b9
Author: Kai Burjack <72760888+kaiburjack at users.noreply.github.com>
Date: Sun Feb 9 13:52:56 2025 +0100
docs: clarify that A-E header needs to be set on bereq.http for pass requests
diff --git a/doc/sphinx/phk/gzip.rst b/doc/sphinx/phk/gzip.rst
index 6a62bf346..e8d997cf0 100644
--- a/doc/sphinx/phk/gzip.rst
+++ b/doc/sphinx/phk/gzip.rst
@@ -70,11 +70,12 @@ Tuning, tweaking and frobbing
In vcl_recv{} you have a chance to modify the client's
Accept-Encoding: header before anything else happens.
-In vcl_pass{} the clients Accept-Encoding header is copied to the
+In vcl_pass{} the client's Accept-Encoding header is copied to the
backend request unchanged.
-Even if the client does not support gzip, you can force the A-C header
-to "gzip" to save bandwidth between the backend and varnish, varnish will
-gunzip the object before delivering to the client.
+Even if the client does not support gzip, you can force the A-E header
+to "gzip" on bereq.http in vcl_backend_fetch{} to save bandwidth between
+the backend and varnish. Varnish will gunzip the object before delivering
+to the client.
In vcl_miss{} you can remove the "Accept-Encoding: gzip" header, if you
do not want the backend to gzip this object.
More information about the varnish-commit
mailing list