mirrors/caddy-website
1
0
Fork 0
mirror of https://github.com/caddyserver/website.git synced 2025-04-24 14:06:17 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions

docs: Minor tweaks, clarifications.

Browse source
This commit is contained in:
Matthew Holt 2020-04-01 11:09:26 -06:00
parent 3ecf039665
commit 836e15afbc
No known key found for this signature in database
GPG key ID: 2A349DD577D586A5
4 changed files with 8 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

3
src/docs/markdown/caddyfile/directives/reverse_proxy.md
View file

@ -52,7 +52,7 @@ reverse_proxy [<matcher>] [<upstreams...>] {
- **&lt;upstreams...&gt;** is a list of upstreams (backends) to which to proxy.
- **to** is an alternate way to specify the list of upstreams, one (or more) per line.
Upstream addresses can take the form of a conventional [Caddy network address](/docs/conventions#network-addresses) or a URL that contains only scheme and host/port. Valid examples:
Upstream addresses can take the form of a conventional [Caddy network address](/docs/conventions#network-addresses) or a URL that contains only scheme and host/port, with a special exception that the scheme may be prefixed by `srv+` to enable SRV DNS record lookups for load balancing. Valid examples:
- `localhost:4000`
- `127.0.0.1:4000`
@ -60,6 +60,7 @@ Upstream addresses can take the form of a conventional [Caddy network address](/
- `https://example.com`
- `example.com`
- `unix//var/php.sock`
- `srv+http://internal:5099`
Note: Schemes cannot be mixed, since they modify the common transport configuration (a TLS-enabled transport cannot carry both HTTPS and plaintext HTTP). Specifying ports 80 and 443 are the same as specifying the HTTP and HTTPS schemes, respectively. Any explicit transport configuration will not be overwritten, and omitting schemes or using other ports will not assume a particular transport. Additionally, schemes cannot contain paths or query strings, as that would imply simultaneous rewriting the request while proxying, which behavior is not defined or supported.