mirror of
https://github.com/caddyserver/website.git
synced 2025-04-22 13:06:16 -04:00
docs: Mention compression header behaviour in reverse_proxy
(#193)
* 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. * Update src/docs/markdown/caddyfile/directives/reverse_proxy.md Perfect! Co-authored-by: Francis Lavoie <lavofr@gmail.com> Co-authored-by: Francis Lavoie <lavofr@gmail.com>
This commit is contained in:
parent
c60bf706a1
commit
578394fc5f
1 changed files with 1 additions and 0 deletions
|
@ -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, when using the [`http` transport](#the-http-transport), the `Accept-Encoding: gzip` header will be set, if it is missing in the request from the client. This behavior can be disabled with [`compression off`](#compression) on the transport.
|
||||
|
||||
#### HTTPS
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue