Caddy is an open-source web server and reverse proxy designed to make modern HTTPS deployments simpler. Written in Go, it combines a web server, automatic TLS certificate management, reverse proxy, static file server, and extensible module system in a single application.
Its biggest differentiator is automatic HTTPS. When configured with a domain name, Caddy can obtain and renew certificates and redirect HTTP traffic to HTTPS without requiring the extensive certificate configuration often associated with traditional web servers.
Features
Caddy supports HTTP/1.1, HTTP/2, and HTTP/3, with modern protocols enabled by default. It can serve static websites and files, or act as a reverse proxy in front of applications and services.
The Caddyfile provides a relatively simple configuration syntax for common deployments, while Caddy's native JSON configuration and API provide considerably more control for advanced setups. Configuration adapters also allow other formats to be converted into Caddy's native configuration model.
The reverse proxy supports multiple upstreams, load balancing, active and passive health checking, retries, connection pooling, header manipulation, buffering, and different transport options. This makes Caddy capable of handling substantially more than a basic single-backend proxy.
Caddy's TLS system can automatically obtain publicly trusted certificates using supported ACME issuers, while its internal CA can be used for internal services and local development. It also supports features such as multi-issuer fallback and Encrypted ClientHello.
The architecture is highly modular. Caddy functionality is implemented through modules, allowing additional capabilities to be added without modifying the core application. The official project also provides an extensive plugin ecosystem.
Download Caddy v2.11.9 - Software Mirrors |
|---|
Caddy v2.11.9 for Windows |
Caddy v2.11.9 for macOS |
Caddy v2.11.9 for Linuxcaddy_2.11.9_linux_s390x.tar.gz | 16.54 MB caddy_2.11.9_linux_s390x.deb | 16.57 MB caddy_2.11.9_linux_riscv64.tar.gz | 16.32 MB caddy_2.11.9_linux_riscv64.deb | 16.35 MB caddy_2.11.9_linux_ppc64le.tar.gz | 15.61 MB caddy_2.11.9_linux_ppc64le.deb | 15.64 MB caddy_2.11.9_linux_armv7.tar.gz | 16.3 MB caddy_2.11.9_linux_armv7.deb | 16.32 MB caddy_2.11.9_linux_armv6.tar.gz | 16.32 MB caddy_2.11.9_linux_armv6.deb | 16.34 MB caddy_2.11.9_linux_armv5.tar.gz | 16.32 MB caddy_2.11.9_linux_armv5.deb | 16.35 MB caddy_2.11.9_linux_arm64.tar.gz | 15.59 MB caddy_2.11.9_linux_arm64.deb | 15.61 MB |
Caddy v2.11.9 for BSDcaddy_2.11.9_freebsd_armv7.tar.gz | 16.22 MB caddy_2.11.9_freebsd_armv6.tar.gz | 16.24 MB |
Others Download related to Caddy v2.11.9caddy_2.11.9_src.tar.gz | 11.82 MB |
Caddy v2.11.9 Source Code |
Caddy v2.11.9 Release Notes:This is a quick follow-up on top of 2.11.8, to fix a regression it introduced and a few more security issues, mostly in FastCGI. It contains only fixes backported from master, plus a couple of small additions. If you're on 2.11.8 and serve PHP, we recommend upgrading. Huge thank you to our sponsors for keeping the project alive with resources, and for our maintainers who triage and assist tirelessly in this relentless new age of AI.Highlights
:warning: Breaking changes
Security fixesThank you to everyone who reported responsibly and helped with patches:
go.mod file. Please ONLY upgrade the Caddy dependency if there's a change to an exported API your plugin uses.
What's Changed
|
Performance and Compatibility
Caddy is written in Go and compiles for major platforms without requiring external runtime dependencies. It can be deployed directly as a binary, in containers, or through other supported installation methods.
Its performance is strong enough for production web serving and reverse-proxy workloads, while the configuration model is arguably its bigger advantage over traditional alternatives. A simple reverse proxy can be configured with only a few lines, while more complex deployments can use the JSON API and modular configuration system.
Caddy is particularly attractive for administrators who regularly deploy HTTPS services. Automatic certificate provisioning and renewal remove much of the routine TLS maintenance, while the same configuration can handle reverse proxying, static files, headers, compression, and other HTTP functions.
There is a learning curve once deployments move beyond simple Caddyfile configurations. Caddy's underlying JSON configuration and modular architecture are powerful, but understanding modules, matchers, handlers, transports, and adapters takes time.
For administrators migrating from Nginx or Apache, Caddy's configuration model is also substantially different. Existing configurations cannot simply be copied over, although Caddy provides configuration adapters for several formats.
System Requirements
Windows, Linux, macOS, or another supported platform
64-bit or platform-appropriate Caddy binary
Network access for public certificate issuance and renewal when using publicly trusted HTTPS certificates
Ports 80 and 443 when using standard public HTTPS with automatic certificate management
Additional storage and resources depending on website, proxy, logging, and workload requirements
Pros and Cons
Pros
Automatic HTTPS and certificate renewal
HTTP/1.1, HTTP/2, and HTTP/3 support
Simple Caddyfile configuration
Powerful JSON configuration and API
Excellent reverse-proxy capabilities
Load balancing and health checking
Static file server
Highly extensible modular architecture
Cross-platform
No external runtime dependencies
Supports internal HTTPS with its own CA
Suitable for containers and modern infrastructure
Strong support for automated deployments
Cons
Configuration becomes more complex for advanced deployments
Different configuration model from Nginx and Apache
Large plugin ecosystem can make choosing extensions more complicated
Some advanced functionality requires understanding Caddy's module architecture
Automatic HTTPS still requires correct DNS and network configuration for public services
Migration from existing Nginx or Apache configurations requires rewriting the configuration
How to Install
Download the appropriate Caddy package for your operating system or use one of the supported installation methods.
For a basic HTTPS website, create a Caddyfile containing the domain and the desired handler. For example:
example.com {
reverse_proxy localhost:9000
}Run Caddy with the configuration file. If the domain resolves to the server and ports 80 and 443 are reachable, Caddy can automatically obtain and manage the TLS certificate.
For containerized deployments, Caddy can also be run as a Docker container with configuration and certificate storage mounted as persistent volumes.
Before deploying a configuration, caddy validate can be used to verify the configuration, while caddy reload allows configuration changes to be applied without stopping the running server.
Final Verdict
Caddy is one of the strongest choices for administrators who want a modern web server and reverse proxy without spending significant time managing TLS certificates.
Its automatic HTTPS is the standout feature, but the software offers considerably more than certificate automation. HTTP/3, load balancing, health checks, static file serving, API-driven configuration, and a powerful module architecture make it capable of handling serious production workloads.
Its main weakness is complexity at the advanced end. Caddy is extremely approachable for simple deployments, but administrators who need highly customized routing and modular behavior will need to learn its underlying configuration architecture.
For new deployments, especially reverse proxies and HTTPS services, Caddy offers an excellent balance of simplicity, automation, and production capability.
Post a Comment/Report Broken Link: