Caddy v2.11.7 released on 03-10-2026
Caddy v2.11.7 is out now. It fixes regressions introduced in v2.11.6 around idle read/write timeouts, resolves an HTTP/2 reverse-proxy panic and dropped streams, and adds support for the Incremental header (RFC 10036), helping streaming apps and reverse-proxy users.
See the project’s GitHub release notes and full changelog for details and upgrade instructions: https://github.com/caddyserver/caddy/compare/v2.11.6…v2.11.7
What’s in this release
- Fixes for regressions from v2.11.6: idle read/write timeouts that caused an HTTP/2 reverse-proxy panic when reading a request body after the handler returned, and HTTP/1.1 streaming responses being cut off after 60 seconds (#8101, #8103, fixed in #8107).
- Support for the Incremental header field (RFC 10036): reverse_proxy will forward Incremental: ?1 immediately and encode will stream instead of buffering; if request_buffers or response_buffers prevent incremental forwarding, Caddy returns 501 Not Implemented and can add a Proxy-Status header via proxy_status_name (#8020).
- Reliability and performance improvements: faster TLS handshakes when CertMagic skips unused event data, listeners moved off Unix sockets now close and unlink immediately on reload, headers handler preserves multiple Set-Cookie values, and caddy fmt no longer drops a trailing opening brace (#8010, #8061, #8080, #8047).
Upgrade notes
- If you are on v2.11.6, upgrading to v2.11.7 is recommended to avoid the timeout and streaming regressions.
- When using Incremental responses, check reverse_proxy request_buffers and response_buffers settings: if they would force buffering, Caddy will return 501 Not Implemented and can include a Proxy-Status header explaining why—adjust buffer settings or use proxy_status_name for diagnostic information.
Share any comments on your upgrade experience or whether streaming behaviour and proxy stability improved; upstream issue trackers and community channels are the appropriate places for detailed reports.
