2.0 beta 8

Caddy 2.0 beta 8 is the next pre-release in the development cycle of Caddy 2 and is the best update yet! Some highlights:

• Logging! Caddy 2 has an exceptionally powerful, flexible, and high-performing log. Read the docs about logging.
• Rewrite handler can now quickly strip path prefix or suffix conveniently, and issue HTTP redirects
• Significant improvements to TLS certificate management, especially at large scale. Give Caddy 2 a million domains and it will gradually obtain certificates for them with built-in rate limiting and retries over the course of days or weeks.
• CI improvements, including continuous fuzzing.
• HTTP cache can be configured to work in a group/cluster setting.
• Several bug fixes, including a hotfix for silly bug in beta 7 (d'oh! 🤦‍♂️)

See all commits since beta 6 here.

Please remember that Caddy 2 beta releases are not yet feature-complete as development is ongoing, nor are they stable; there are likely to be some breaking changes between tags. We hope you will find ways to use Caddy 2 beta in production and report any issues you find!

Thank you to all of you who have reported bugs or requested features so far. We continue to make good progress.

To learn how to get started, see the README on the v2 branch.

This is a community effort, so please report bugs, join the discussion, and submit pull requests to be a part of the team!

Support:

• Community forum to ask questions, get community support, and lend your help
• Issue tracker for bug reports and dev discussion

v2 Resources:

• Quick Start
• Full documentation
• Writing a v2 config from scratch
• Caddyfile examples
• Writing a Caddy 2 module

2.0 beta 7

Matt made an oops on this release, it has a bug serving HTTP requests; please use beta 8 instead.

2.0 beta 6

Caddy 2.0 beta 6 is the next pre-release in the development cycle of Caddy 2 and is the biggest update yet! Some highlights:

• Migrated all WIP and completed enterprise features to open source, including:
  • /config and /id API endpoints, which enable config traversal (selective updates) and exporting current configuration
  • WIP cache plugin for HTTP responses
  • pem_loader plugin, for specifying TLS certs and keys directly in config
  • distributed_stek plugin, for high-performance TLS session resumption in clusters
  • Custom TLS certificate selection policies
  • WIP Starlark handler (embedded scripting language)
• New placeholders for RemoteAddr (client IP, etc.)
• HTTP basic authentication plugin
• reverse_proxy: Ability to customize ServerName value in TLS handshake to backends
• reverse_proxy: Dynamic backends using placeholders (variables) in dial address
• reverse_proxy: Minor optimization of MaxIdleConnsPerHost default value

See all commits since beta 4 here.

(We tagged beta 5 mid-cycle as a test, but made a mistake with a dependency so we're ignoring that tag.)

Be advised that the next beta release may be delayed as we transition a bunch of code to open source and work on a new website and official images/packages.

Please remember that Caddy 2 beta releases are not yet feature-complete as development is ongoing, nor are they stable; there are likely to be some breaking changes between tags. We hope you will find ways to use Caddy 2 beta in production and report any issues you find!

Thank you to all of you who have reported bugs or requested features so far. We've made good progress.

To learn how to get started, see the README on the v2 branch.

This is a community effort, so please report bugs, join the discussion, and submit pull requests to be a part of the team!

Support:

• Community forum to ask questions, get community support, and lend your help
• Issue tracker for bug reports and dev discussion

v2 Resources:

• Quick Start
• Full documentation
• Writing a v2 config from scratch
• Caddyfile examples
• Writing a Caddy 2 module

2.0 beta 4

Caddy 2.0 beta 4 is the next pre-release in the development cycle of Caddy 2. Some highlights:

• Plugged in the JSON 5 and JSON-C config adapters
• New file-server and reverse-proxy commands for convenience
• reverse_proxy module: Make request retries configurable based on properties of the request
• adapt subcommand: Default --adapter value is "caddyfile"
• Several bug fixes

See all commits since previous tag here.

Be advised that the next beta release may be delayed as we transition a bunch of code to open source and work on a new website.

Please remember that Caddy 2 beta releases are not yet feature-complete as development is ongoing, nor are they stable; there are likely to be some breaking changes between tags. We hope you will find ways to use Caddy 2 beta in production and report any issues you find!

Thank you to all of you who have reported bugs or requested features so far. We've made good progress.

To learn how to get started, see the README on the v2 branch.

This is a community effort, so please report bugs, join the discussion, and submit pull requests to be a part of the team!

Support:

• Community forum to ask questions, get community support, and lend your help
• Issue tracker for bug reports and dev discussion

v2 Resources:

• Quick Start
• Full documentation
• Writing a v2 config from scratch
• Caddyfile examples
• Writing a Caddy 2 module

2.0 beta 3

Caddy 2.0 beta 3 is the next pre-release in the development cycle of Caddy 2. Some highlights:

• Added CLI help (run caddy or caddy help <command> to get help)
• Added validate subcommand to validate configurations
• Renamed adapt-config subcommand to adapt and renamed --input to --config and --config-adapter to --adapter and --print-env to --environ
• Added --validate flag to adapt subcommand to validate adapted configs
• CLI commands are now extensible from modules
• Ability to customize trusted roots for ACME servers
• Configurable renewal and OCSP check intervals for certificate management
• New email and acme_ca global options for the Caddyfile
• not matcher can now be used in the Caddyfile
• Several bug fixes, especially with the Caddyfile

See all commits since previous tag here.

Please remember that Caddy 2 beta releases are not yet feature-complete as development is ongoing, nor are they stable; there are likely to be some breaking changes between tags. We hope you will find ways to use Caddy 2 beta in production and report any issues you find!

Thank you to all of you who have reported bugs or requested features so far. We've made good progress.

To learn how to get started, see the README on the v2 branch.

This is a community effort, so please report bugs, join the discussion, and submit pull requests to be a part of the team!

Support:

• Community forum to ask questions, get community support, and lend your help
• Issue tracker for bug reports and dev discussion

v2 Resources:

• Quick Start
• Full documentation
• Writing a v2 config from scratch
• Caddyfile examples
• Writing a Caddy 2 module

2.0 beta 2

Caddy 2.0 beta 2 is the next pre-release in the development cycle of Caddy 2. Notable changes:

• You can now perform substring or regular expression replacements in headers
• The reverse proxy allows header manipulation: add, set, remove, and substring/regexp replacements
• Renamed static_response Caddyfile directive to respond
• Updated certmagic, so (1) long-expired certificates are cleaned up from storage, and (2) Caddy will attempt to replace a revoked certificate with a new one automatically
• Ability to configure storage with the Caddyfile
• Several bug fixes and improvements

See all commits since previous tag here.

Please remember that Caddy 2 beta releases are not yet feature-complete, as development is ongoing, nor are they stable; there are likely to be some breaking changes between tags. We hope you will find ways to use Caddy 2 beta in production and report any issues you find!

Thank you to all of you who have reported bugs or requested features so far. We've made good progress.

To learn how to get started, see the README on the v2 branch.

This is a community effort, so please report bugs, join the discussion, and submit pull requests to be a part of the team!

Support:

• Community forum to ask questions, get community support, and lend your help
• Issue tracker for bug reports and dev discussion

v2 Resources:

• Quick Start
• Full documentation
• Writing a v2 config from scratch
• Caddyfile examples
• Writing a Caddy 2 module

2.0 beta 1

The first beta/development release is here! v2.0.0-beta1 is functional enough to serve most sites and may be used in production after you test it and find that it meets your needs. Caddy 2 is not backwards-compatible with Caddy 1.

Caddy 2 beta releases are not feature-complete or free of bugs, but we hope to release beta version regularly until the release candidates later this year. Beta releases may also have breaking changes, so please be aware of the changes as we continue developing Caddy 2.

To learn how to get started, see the README on the v2 branch: https://github.com/caddyserver/caddy/tree/v2

This is a community effort, so please report bugs, join the discussion, and submit pull requests to be a part of the team!

Support:

• Community forum to ask questions, get community support, and lend your help
• Issue tracker for bug reports and dev discussion

v2 Resources:

• Quick Start
• Full documentation
• Writing a v2 config from scratch
• Caddyfile examples
• Writing a Caddy 2 module

1.0.3

v1.0.3

1.0.2

This release uses Go 1.12.8 to patch the HTTP/2 implementation against the security vulnerabilities reported today.

One minor breaking change in Go 1.12.8 might affect some configurations that use service name in the port of their Caddyfiles, like so: example.com:https - we've smoothed this over so the behavior of Caddy is the same but if you encounter any odd inconsistencies, switch to using numeric ports or proper URL scheme: either https://example.com (recommended) or example.com:443.

1.0.1

Caddy 1.0.1 introduces a number of fixes and improvements, and deprecates the max_certs subdirective of tls (using it still enables on-demand TLS but you should use ask for proper protection).

KNOWN ISSUE: Building Caddy with plugins is difficult due to the repository move. Our build server has been patched to make it work, but plugin authors will need to update import paths. (Sorry! Unexpected.) I've done my best to file issues with all registered plugins.