From 644784bfa4726426ace1a4caed147544cae2d000 Mon Sep 17 00:00:00 2001 From: Paulo Vieira Date: Mon, 6 Sep 2021 09:58:34 +0100 Subject: [PATCH] Update reverse_proxy.md Documantion says: "By default, Caddy passes thru incoming headers [...], with two exceptions:". But technically there is another another header that is added (if not present): `Accept-Encoding`. When the client is a web browser this header should be already set. But for curl or similar tools, that might not be the case. --- src/docs/markdown/caddyfile/directives/reverse_proxy.md | 1 + 1 file changed, 1 insertion(+) diff --git a/src/docs/markdown/caddyfile/directives/reverse_proxy.md b/src/docs/markdown/caddyfile/directives/reverse_proxy.md index fdbd6bd..d43934d 100644 --- a/src/docs/markdown/caddyfile/directives/reverse_proxy.md +++ b/src/docs/markdown/caddyfile/directives/reverse_proxy.md @@ -201,6 +201,7 @@ By default, Caddy passes thru incoming headers to the backend—including th - It adds or augments the [X-Forwarded-For](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Forwarded-For) header field. - It sets the [X-Forwarded-Proto](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Forwarded-Proto) header field. +Additionally, Caddy will also set `Accept-Encoding: gzip` if that header is missing in the request from the client. This behavior can be disabled by setting `compression off` in the `http` transport. #### HTTPS