Shipped · DevOps and infrastructure

What caddyserver/caddy shipped

The public repository of Caddy · github.com/caddyserver/caddy

Written by FoxPlug from the repository's own releases; not affiliated with Caddy. Paste your own repository in the box below and FoxPlug writes the same weekly update for your product. This page is an automatic summary of the releases, pull requests and commits in github.com/caddyserver/caddy; Caddy did not write it and does not use or endorse FoxPlug. Every line links to the change it describes.

Get a weekly update like this for your product, free

Or Use it as a GitHub Action

See the update FoxPlug writes for caddy, free

Week of November 9, 2026

What shipped

Why it matters

This week's changes fix several edge cases that could silently change behavior: health checks against mixed TLS and plain-HTTP ports now use the right scheme, and very large transfers with a minimum rate are no longer cut off. Two changes tighten or clarify configuration behavior: client cert verification modes now require a trust pool, and fileserver try_files keeps trailing-slash matches on the site root. Storage archive export on Windows and temp file cleanup in tests also got fixes.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

This week: min_rate no longer cuts off transfers over 8.59 GiB, health checks pick the scheme by port, client cert verify modes now require a trust_pool, try_files keeps root directory matches, and Windows archive export writes slash paths.

Post for LinkedIn

Changes this week in Caddy: transfers larger than about 8.59 GiB are no longer cut off when a minimum rate is set, and active health checks now choose their scheme by the port they connect to, so plain-HTTP management ports work behind TLS upstreams. Client certificate verification modes verify_if_given and require_and_verify now fail to load without a trust_pool instead of quietly using system roots. try_files keeps the explicit trailing slash when a candidate cleans to the site root, storage archive export writes slash-separated paths so Windows imports work, relative config directories are hidden, and test Caddyfile imports clean up their temp files.

Week of November 2, 2026

What shipped

Why it matters

This week centers on security hardening in FastCGI and the file server, with a release that backports the fixes. Anyone serving PHP or relying on path matchers should upgrade, since several fixes close ways to reach files that matchers did not intend to expose.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

V2.11.9 is out: fixes a regression from 2.11.8 plus several FastCGI security fixes, including env headers overriding HTTP_ variables and crafted paths selecting other scripts. Also: file server, Caddyfile and reverse proxy fixes. Upgrade if you serve PHP.

Post for LinkedIn

Caddy v2.11.9 is released, a quick follow-up to 2.11.8 that fixes a regression it introduced and several security issues, mostly in FastCGI. If you are on 2.11.8 and serve PHP, upgrading is recommended. Highlights this week: - FastCGI: configured env variables now take precedence over request headers, and paths whose escaped form selects another script are rejected. - FastCGI: rejects Windows 8.3 short-name aliases and alternate data stream paths, and takes HTTP_HOST only from the routed host. - php_fastcgi rewrites to index.php only when it exists. - File server: rejects regular files addressed with a trailing separator, and applies slash rules to the fallback entry. - Caddyfile: unbalanced brace site blocks and negative import indices are now rejected. - TLS policy merging reports confli

Week of October 26, 2026

What shipped

Why it matters

This week's changes close several path handling and header copying gaps that could send users to the wrong origin or leak hop-by-hop fields, and they fix auth and TLS configuration behavior that silently ignored settings. For anyone running Caddy in containers or behind FastCGI, the data directory and response body fixes remove failure modes that were hard to diagnose from logs alone.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

This week in Caddy: php_fastcgi redirects stay on the same origin, the file matcher ignores trailing-slash paths that point at regular files, FastCGI responses stop at the declared Content-Length, hop-by-hop headers are stripped when copying response headers, and basic_auth accep

Post for LinkedIn

This week's Caddy changes focus on correctness in path and header handling. The php_fastcgi directory redirect now stays on the same origin, the file matcher no longer treats a trailing-slash path as a regular file, and the file matcher remainder is escaped before rewriting. Response header copying now strips hop-by-hop headers such as Alt-Svc and Keep-Alive, and the FastCGI transport stops at the declared Content-Length so extra bytes from a responder no longer break HTTP/1.1 or HTTP/2 clients. Auth also changed: basic_auth checks username uniqueness after placeholder expansion and now looks up third-party hash modules by name.

Week of October 19, 2026

What shipped

Why it matters

This week touched several parts of the reverse proxy that affect real deployments: retries through forward proxies, trailer preservation, interim response headers, upgrade cleanup and upstream tracing. It also fixed several correctness and reliability issues in placeholders, Windows service status, logging filters and client certificate verification.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

This week: tls matcher gains CEL support, reverse proxy emits OpenTelemetry client spans and preserves request trailers, file placeholder lookups are cached and capped, Windows service status updates are serialised, and more.

Post for LinkedIn

This week in Caddy: the tls matcher now supports CEL expressions, so it works inside expression matchers. The reverse proxy emits OpenTelemetry client spans for upstream requests, preserves request trailer values, strips hop-by-hop headers from 1xx interim responses, retries dial errors wrapped by a forward proxy, and closes backend bodies and hijacked sockets when upgrade setup fails. File placeholder replacements are now cached and capped at 1000 to avoid timeouts, Windows service status updates are serialised, and logging fixes correct query filter redaction and reject out-of-range ip_mask CIDRs.

Week of October 12, 2026

What shipped

Why it matters

This week fixed several bugs that affected real deployments: a reverseproxy security revert around health check redirects, truncated request bodies being forwarded with a 200, broken directory log creation and CRLF issues in hash-password. It also added experimental WebTransport passthrough and listener-specific TLS policy isolation. Users of reverse_proxy, logging, basic_auth and FastCGI get concrete behavior changes to check against their configurations.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

This week in Caddy: reverted health check redirect handling in reverse_proxy over a credential leak risk, fixed truncated request bodies returning 200, independent conditional header defaults, 302 for FastCGI Location responses, corrected log directory modes, and experimental Web

Post for LinkedIn

This week in Caddy: a reverseproxy revert around health check redirect destinations, because a backend-controlled cross-origin redirect could leak custom secrets or TLS client credentials; a fix so requests cut short by request_body max_size return 413 instead of being forwarded truncated; conditional header defaults now evaluated independently; FastCGI Location responses without Status use 302; logging dir_mode from_file creates directories as 0700; hash-password handles CRLF and input without a trailing newline; TLS policies cloned across listeners; and experimental WebTransport passthrough for reverse_proxy.

Week of October 5, 2026

What shipped

Why it matters

This week resolves a set of bugs that affect correctness of proxying, logging and file serving, including retry loops that resend requests, lost headers after informational responses, and case sensitive log host matching. Sites using encoding, templates, fastcgi, TLS ECH, Caddyfile imports or symlinked browse listings also get fixes for incorrect headers, misleading errors and panics. Together these improve reliability for existing configurations without requiring changes to them.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

This week: retries no longer resend on request-only conditions, satisfied route groups skip matchers, headers survive 103 Early Hints, repeated expression matchers are rejected, expired body read deadlines are kept, and HEAD encode responses drop the empty stream length.

Post for LinkedIn

This week Caddy fixed several issues that affect how existing configurations behave. Expression based lb_retry_match now only retries when the expression uses response data, so request-only conditions no longer cause extra upstream attempts. Routes in an already matched group skip their matchers, avoiding matcher errors. Headers set before proxying are kept after 103 Early Hints and other informational responses. The Caddyfile parser now rejects repeated expression matchers instead of dropping them. Expired request body read deadlines are preserved for timed out HTTP/1 uploads. Host matching in logger_names is case insensitive. Encoding no longer sets an empty stream trailer as Content-Length on HEAD responses. Weighted round robin no longer panics with fewer weights than upstreams, and ra

Week of September 28, 2026

What shipped

Why it matters

This week addresses critical regressions in 2.11.6 affecting proxying stability and timeout behavior, while adding important standards support. The fixes around request body deadlines, stream lifecycle management, and timeout precedence solve production issues where long-lived connections and configuration reloads could cause crashes or hangs.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

V2.11.7 is out. We fixed HTTP/2 proxy crashes, timeout override issues, stream lifecycle problems, and added RFC 10036 Incremental header support. Upgrade recommended if on 2.11.6.

Post for LinkedIn

V2.11.7 addresses critical regressions from 2.11.6. Key fixes include HTTP/2 proxy crashes when streams timed out after a minute, request body timeouts being overridden by server settings, data races in stream detachment, and proper Set-Cookie header handling. We also added RFC 10036 Incremental header support. Upgrade recommended for 2.11.6 users.

Week of September 21, 2026

What shipped

Why it matters

This week focused on correctness: fixing placeholder expansion that was silently corrupting user data, HTTP/3 TLS verification being ignored, and response handling issues. These bugs affected core features like reverse proxying, authentication, and request body processing.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

This week's fixes address placeholder expansion corrupting credentials and JSON bodies, HTTP/3 TLS verification being silently ignored, and partial response buffering. Several correctness improvements across auth, request handling, and reverse proxy.

Post for LinkedIn

This week's releases focus on data correctness and security. Fixes include placeholder expansion that was silently corrupting authentication credentials and JSON request bodies, HTTP/3 reverse proxies now respecting configured CA certificates instead of ignoring them, proper 413 status for oversized request bodies, and corrected response flushing behavior. These improvements affect core features like authentication, reverse proxying, and request body handling.

Weeks with too little public activity are left out rather than filled in. Last updated 2026-11-16.

Is this your repo? Ask us to remove this page.

Leaderboard