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.

1.0.0

We did it! Caddy 1.0 is here. Future changes on the 1.0 tree will focus on stability and bug fixes.

Go modules are required to build Caddy from source. Go 1.13 will use modules by default.

Notably, binaries are no longer licensed with a separate EULA. Commercial use of our download page, however, still requires a subscription (all customers have been grandfathered in -- in effect, nothing is really different except we got rid of the annoying legal technicality).

CHANGES:

• Minor internal/linting improvements
• EULA no longer applies
• Backwards compatibility goal

1.0.0-beta2

We continue to improve Caddy's compatibility with Go modules. Beta 2 improves Caddy's build process. Separate build scripts are no longer required, and Caddy can be built with a custom selection of plugins without any modifications to Caddy's source code. See the README/wiki for instructions.

Please report any bugs you find, especially if there are regressions due to updates for compatibility (a significant refactoring of CertMagic was recently folded in).

• Continue migration to Go modules
• Eliminate need for special build script
• Internal changes for better compatibility

1.0.0-beta1

During this beta period, the build server will be undergoing maintenance. If you encounter issues downloading, please use these GitHub releases to get Caddy builds (or build from source) in the meantime.

Full change list:

• Major internal changes (Go modules & remove vendor)
• Rename -env flag to -envfile
• New -env flag to print the environment
• New 'dyndns' directive
• proxy: Manipulate headers using regular expressions
• A few bug fixes

0.11.5

Caddy 0.11.5 is built with Go 1.12 and brings TLS 1.3 to all worthy TLS connections by default. We've also re-allowed HEAD requests on static files and organized the startup output a little better.

(If you need to enable TLS 1.0 or 1.1 -- please don't -- you now have to specify TLS 1.0 or TLS 1.1 ciphers, as those ciphers have been removed from the default cipher suite listing.)

Full change log:

• TLS 1.3
• Built with Go 1.12
• More organized output at startup
• internal: Paths are now hidden from other middlewares
• staticfiles: Allow HEAD method
• tls: TLS 1.3 default max version (1.2 still default min)
• tls: Better handling of empty ACME email addresses
• tls: Removed CBC ciphers from defaults
• Other minor improvements and bug fixes