mirror of
https://github.com/caddyserver/caddy.git
synced 2024-12-27 22:23:48 +03:00
260982b2df
This makes it more convenient to configure quick proxies that use HTTPS but also introduces a lot of logical complexity. We have to do a lot of verification for consistency and errors. Path and query string is not supported (i.e. no rewriting). Scheme and port can be inferred from each other if HTTP(S)/80/443. If omitted, defaults to HTTP. Any explicit transport config must be consistent with the upstream schemes, and the upstream schemes must all match too. But, this change allows a config that used to require this: reverse_proxy example.com:443 { transport http { tls } } to be reduced to this: reverse_proxy https://example.com which is really nice syntactic sugar (and is reminiscent of Caddy 1). |
||
---|---|---|
.. | ||
caddyauth | ||
encode | ||
fileserver | ||
headers | ||
httpcache | ||
requestbody | ||
reverseproxy | ||
rewrite | ||
standard | ||
templates | ||
autohttps.go | ||
caddyhttp.go | ||
errors.go | ||
marshalers.go | ||
matchers.go | ||
matchers_test.go | ||
replacer.go | ||
replacer_test.go | ||
responsewriter.go | ||
routes.go | ||
server.go | ||
staticerror.go | ||
staticresp.go | ||
staticresp_test.go | ||
subroute.go | ||
vars.go |