Caddy 2.11.7 upgrade: fixes 2.11.6 crash and dropped streams
Summary
Caddy 2.11.7 is a patch release that fixes regressions from 2.11.6. The 2.11.6 default idle read/write timeouts caused trouble, and this release corrects it. It also adds support for the new Incremental header (RFC 10036). The maintainers recommend upgrading if you are on 2.11.6.
Breaking changes and deprecations
Reported by the project (not tested by us): no breaking changes are listed. One new behaviour to know about: if an upstream sends Incremental: ?1 and your request_buffers or response_buffers settings would stop incremental forwarding, reverse_proxy now answers 501 Not Implemented, as the RFC requires. The new proxy_status_name option adds a Proxy-Status header to explain such refusals.
Tested in our lab
We installed 2.11.6 from the official Caddy apt repository on Debian 13, ran a small Caddyfile, stopped the service, upgraded the package to 2.11.7 and started it again.
- The service came back up, the existing Caddyfile worked unchanged, and the journal showed no warnings or errors.
- The cookie placeholder regression is visible in 2.11.6 and fixed in 2.11.7. With no cookie in the request, a
headervalue using{http.request.cookie.foo}was output literally on 2.11.6. On 2.11.7 it is empty. With the cookie present, both versions output its value.
We did not test the HTTP/2 crash, the 60-second stream cuts, the Incremental header, Unix socket reloads or the Set-Cookie change.
Lab log
$ caddy version
v2.11.6 h1:sWxeamdlCZvcH4qeDz8bB0mdxgfYTeqV7HxOjXyIRas=
$ curl -si http://localhost:8080/
HTTP/1.1 200 OK
Content-Type: text/plain; charset=utf-8
Server: Caddy
X-Cookie: [{http.request.cookie.foo}]
[...]
$ systemctl stop caddy
$ apt-get install -y -qq caddy=2.11.7
Setting up caddy (2.11.7) ...
$ systemctl start caddy
$ caddy version
v2.11.7 h1:yj0Y4fYZGPkSvibBJ1sTWE33xC0fxztVyXEW5iIdUT4=
$ systemctl is-active caddy
active
$ curl -si http://localhost:8080/
HTTP/1.1 200 OK
Content-Type: text/plain; charset=utf-8
Server: Caddy
X-Cookie: []
[...]
$ curl -si http://localhost:8080/ -H "Cookie: foo=bar"
[...]
X-Cookie: [bar]
$ journalctl -u caddy --no-pager -p warning -n 5
-- No entries --
The test Caddyfile was:
:8080 {
header X-Cookie "[{http.request.cookie.foo}]"
respond "hello" 200
}
Reported by others
The release notes (reported by the project, with PRs linked there) say 2.11.6 could panic over HTTP/2 when the reverse proxy was still reading a request body (#8101), cut off HTTP/1.1 streaming responses after 60 seconds (#8103), and reset quiet HTTP/2 streams (#8118). All are listed as fixed. Other listed changes: separate Set-Cookie fields from JSON set, immediate Unix socket cleanup on reload, a caddy fmt fix, and faster TLS handshake lookups.
Source: https://github.com/caddyserver/caddy/releases/tag/v2.11.7
Verdict
Upgrade now if you run 2.11.6, especially with reverse proxying, SSE or other streaming. If you are on an earlier version, there is no urgent need, but nothing we saw argues against upgrading.