From d9bf019237751ef7123f56f7fd9f538298e635ef Mon Sep 17 00:00:00 2001 From: Ali Date: Thu, 23 Apr 2026 03:25:45 +0500 Subject: [PATCH] docs: note ETag handling in response compression task When a response is compressed, Envoy strips strong ETags by default (weak ETags are preserved). Users discovering this at runtime was the source of some confusion; add a short section that documents the default and links to the upstream Envoy compressor filter docs for the tunable options (disable_on_etag_header, weaken_etag_on_compress). Fixes #8805 Signed-off-by: Ali --- .../content/en/latest/tasks/traffic/response-compression.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/site/content/en/latest/tasks/traffic/response-compression.md b/site/content/en/latest/tasks/traffic/response-compression.md index 096de8ea43..008783f03f 100644 --- a/site/content/en/latest/tasks/traffic/response-compression.md +++ b/site/content/en/latest/tasks/traffic/response-compression.md @@ -70,6 +70,12 @@ spec: {{% /tab %}} {{< /tabpane >}} +### ETag Handling + +When a response is compressed, Envoy strips strong `ETag` headers by default (weak `ETag`s, prefixed with `W/`, are preserved). This is because compression changes the response body, so the original entity tag no longer identifies the representation that reaches the client. + +See the upstream [Envoy compressor filter documentation](https://www.envoyproxy.io/docs/envoy/latest/configuration/http/http_filters/compressor_filter) for full details of the ETag handling options (`disable_on_etag_header`, `weaken_etag_on_compress`). + ### Configuring Minimum Content Length You can configure the minimum response size for compression using the `minContentLength` field. Responses smaller than this threshold will not be compressed. This can reduce CPU overhead for small responses.