example.com {reverse_proxy {dynamic a example.com 9000}} Get backends dynamically from SRV record DNS queries: example.com {reverse_proxy {dynamic srv _api._tcp.example.com}} Using active health checks and health_upstream can be helpful when creating an intermediate service to do a more thorough health check.

The reverse-proxy command is intended for quick and easy reverse proxies. (You can use it in production if your requirements are simple.) Caddyfile. In the current working directory, create a file called Caddyfile with these contents::2080 reverse_proxy:9000. That config file is roughly equivalent to the caddy reverse-proxy command above.

Common Caddyfile Patterns. This page demonstrates a few complete and minimal Caddyfile configurations for common use cases. These can be helpful starting points for your own Caddyfile documents. ... There are many more reverse_proxy examples here. PHP PHP-FPM. With a PHP FastCGI service running, something like this works for most modern PHP apps:

Or a reverse proxy: localhost {reverse_proxy localhost: 9000} In these examples, file_server and reverse_proxy are directives. Directives are the first word on a line in a site block. In the second example, localhost:9000 is an argument because it appears on the same line after the directive. Sometimes directives can open their own blocks.

By wrapping our site block in curly braces { } we are able to define multiple, different sites in the same Caddyfile. For example::8080 {respond "I am 8080"} ... For example, let's suppose we want to have both a file server and a reverse proxy, but we obviously can't do both on every request! Either the file server will write a response with a ...

Caddyfile. This is the most common way to get HTTPS. Create a file called Caddyfile (no extension) where the first line is your domain name, ... caddy reverse-proxy --from example.com --to localhost:9000. You will see Caddy provision a TLS certificate and serve your site over HTTPS.

@postfoo {method POST path /foo/*} reverse_proxy @postfoo localhost: 9000 Wildcard matchers. The wildcard (or "catch-all") matcher * matches all requests, and is only needed if a matcher token is required. For example, if the first argument you want to give a directive also happens to be a path, it would look exactly like a path matcher!

Examples. Handle requests in /foo/ with the static file server, and other requests with the reverse proxy: example.com {handle /foo/* {file_server} handle {reverse_proxy 127.0.0.1: 8080}} You can mix handle and handle_path in the same site, and they will …

Caddyfile Directives. Directives are functional keywords that appear within site blocks.Sometimes, they may open blocks of their own which can contain subdirectives, but directives cannot be used within other directives unless noted. For example, you can't use basic_auth inside a file_server block, because file_server does not know how to do authentication.

Make a Caddyfile. Stop Caddy if it is already running (Ctrl+C), then run: caddy adapt. Or if you stored the Caddyfile somewhere else or named it something other than Caddyfile: caddy adapt --config /path/to/Caddyfile. You will see JSON output! What happened here? We just used a config adapter to convert our Caddyfile to Caddy's native JSON ...