Log message:
caddy: update to 2.4.5.

2.4.4
-----
This release contains numerous bug fixes, updated dependencies, and QoL
improvements.

Update: This release contains a known regression in the combination of encode
and reverse_proxy modules; please use v2.4.5 instead.

2.4.5
-----
A hotfix for a regression introduced in v2.4.4 related to combining the encode
and reverse_proxy directives.

Log message:
Revbump all Go packages after go117 update

Log message:
Revbump all Go packages after go116 update

Log message:
Revbump all Go packages after go116 update

Log message:
Update caddy to 2.4.3.

v2.4.3

A bug fix for the bug fix, and a couple other bug fixes, including one security
fix for PHP sites. We think all users should upgrade after giving it a whirl in
their test environments. Please note some changes in this patch:

  * In reverse_proxy, the max_idle_conns_per_host option has been removed
    (both Caddyfile and JSON). This may be a breaking change for a few of you,
    but it only breaks configs that relied on a bug. Instead of silently
    failing, you will get an error if you continue using the property. For
    Caddyfile, we basically renamed the property to
    keepalive_idle_conns_per_host. In JSON, we simply removed the property, and
    you should instead set keep_alive/max_idle_conns_per_host if you weren't
    already. Previously, the Caddyfile subdirective set both MaxConnsPerHost
    and MaxIdleConnsPerHost, which was confusing; and the JSON properties
    overwrote each other, so one was removed.
  * Security patch in the FastCGI transport that now sanitizes paths against
    directory traversal outside the site root.
  * Fix canonicalization redirects in file_server. v2.4.2 introduced a bugfix
    for these redirects when used inside handle_path (i.e. rewriting
    the path by stripping a prefix), but caused a regression for many other use
    cases. This release includes a proper fix for all known, tested cases.
    Basically: these redirects are not issued if the filename of a path was
    rewritten internally.

v2.4.2

A few enhancements and bug fixes. Thanks to all who contributed to this
release!

Log message:
Revbump all Go packages after go116 update

Log message:
Update caddy to 2.4.1.

2.4.0

Caddy v2.4.0 is our first stable release of 2021, ushering in over 110 patches
including new features and bug fixes. Thank you to the many contributors who
helped make this possible!

Highlights:

- Secure remote management. You can now enable secure remote access to Caddy's
  admin API! It uses TLS mutual authentication, and you can even define
  permissions for different users.
- Config pull at start. Caddy can be configured to load a different config at
  startup. This is useful if your config is federated through a separate system
  that doesn't have the ability to push configs to Caddy. This feature is
  modular, so configurations can be loaded different ways!
- Server identity management. Caddy can automatically manage its own server
  identity certificate, which can be used when negotiating TLS connections with
  peers. This is required when enabling the secure admin API.
- Self-upgrade command. The new caddy upgrade command will replace the current
  Caddy binary with an upgraded one from our website, with all the same modules
  installed, including third-party plugins that are registered on our site! (We
  can use this code to add/remove modules later, too.)
- Configure other apps from the HTTP Caddyfile. The global options block of the
  Caddyfile now allows configuration of Caddy apps other than HTTP (for
  example, dynamic_dns to keep DNS records pointed at your server with a dynamic
  IP address).
- Caddyfile fmt lint check. When running with a Caddyfile, Caddy will emit a
  warning if the Caddyfile is not formatted with caddy fmt.
- New abort directive. The abort directive is a special case of the
  static_response HTTP handler that prevents an HTTP response by aborting the
  handler chain immediately and forcefully closing the connection.
- New error directive. The error directive returns internal error values in the
  HTTP handler chain, as if an HTTP error had occurred, causing your error
  routes to be invoked.
- Configure response interception from Caddyfile. The reverse_proxy is capable
  of intercepting responses from the backend, and now this is exposed in the
  Caddyfile with handle_response.
- Better caddy list-modules output. Now modules are organized by standard and
  non-standard modules, so you can easily see if a Caddy build has been
  customized.
- Configure logging from Caddyfile. The process logs can now be configured from
  the global options of the Caddyfile.
- Better content negotiation. The file server can now be configured to serve
  precompressed sidecar files, and content encoding preferences are better
  configured and honored.
- Dark mode in directory listings. The file server's "browse" file \ 
listings now
  has a dark mode.
- Removed the logfmt log encoder. It was broken anyways, and its deprecation
  has been warned in previous releases.
- Deprecated common_log format. It will be removed in a future release.
- Deprecated health_path in reverse_proxy directive. It has been replaced with
  health_uri and will be removed in the future.
- Numerous bug fixes and improvements. Thanks for the detailed, helpful bug
  reports! We appreciate your collaboration in making Caddy better.

2.4.1

A small patch release that contains a few noncritical but pleasant fixes
(unless you're using /id/ endpoints in the admin API; then you should
definitely get this update).

Log message:
Revbump all Go packages after go116 update

Log message:
Update caddy to 2.3.0, from pkgsrc-wip.

This version of caddy was super old, and the 2.x versions from wip are
the recommended ones to use.

Log message:
Revbump all Go packages after go115 update