What caddyserver/caddy shipped
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
Week of November 9, 2026
What shipped
- Fixed
min_ratecredit overflow that cut off any single request or response larger than about 8.59 GiB even when the client was far above the configured rate. Pull request #8396 - Active health checks now pick the scheme from the port they connect to, so a plain-HTTP
health_upstreamport excluded withtls_except_portsis checked over HTTP instead of HTTPS. Pull request #8395 - Client certificate verification modes
verify_if_givenandrequire_and_verifynow require atrust_pooland fail to load without one, instead of quietly checking against system roots. Pull request #8394 - Try_files now preserves the explicit trailing slash when a candidate cleans to the site root, keeping the root directory match distinct from a regular file match. Pull request #8391
- Storage archive export now writes slash-separated paths into TAR headers, fixing import failures for keys that contained backslashes on Windows. Pull request #8410
- The config directory is now hidden when it is relative, extending the existing hide fallback. Pull request #8398
- Test Caddyfile imports now clean up their temporary files instead of leaving them in the temp directory. Pull request #8389
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
- Caddyhttp: fix
min_ratecredit overflow on transfers over 8.59 GiB Pull request #8396 - Reverseproxy: pick the health check scheme by the port it connects to Pull request #8395
- Caddytls: require a trust pool for client cert verification modes Pull request #8394
- Fileserver: preserve root directory matching in
try_filesPull request #8391 - Cmd: normalize storage archive paths on Windows Pull request #8410
- Fileserver: hide the config directory when it is relative Pull request #8398
- Testing: clean up temporary Caddyfile imports Pull request #8389
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.
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
- Released v2.11.9, a follow-up to 2.11.8 that fixes a regression it introduced and several more security issues, mostly in FastCGI. Release
- Fixed a FastCGI security issue where request headers could override HTTP_ variables set with the env subdirective. Pull request #8358
- FastCGI now rejects Windows 8.3 short-name aliases and alternate data stream paths that could reach non-PHP files. Pull request #8356
- FastCGI now rejects paths whose escaped form selects a different script than the one path matchers saw. Pull request #8357
- FastCGI now takes HTTP_HOST only from the routed host, so a client-supplied host field cannot override it over HTTP/2. Pull request #8355
- Php_fastcgi rewrites to index.php only when the file exists, avoiding one extra stat per request and wrong matches on sites without index.php. Pull request #8372
- The FastCGI transport now splits the script path at a segment boundary instead of the first.php anywhere. Pull request #8386
- The file server now rejects regular files addressed with a trailing separator, which could bypass path matchers when canonical URIs were disabled. Pull request #8379
- The Caddyfile parser now rejects site blocks with unbalanced braces. Pull request #8375
- Merging TLS policies now reports conflicting
client_authsettings instead of silently keeping the first. Pull request #8306
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
- Released v2.11.9 with fixes backported from master, including several FastCGI security fixes. Release
- Fastcgi: configured env variables now override request headers. Pull request #8358
- Fastcgi: reject Windows 8.3 aliases and alternate data stream paths. Pull request #8356
- Fastcgi: reject paths whose escaped form selects another script. Pull request #8357
- Fastcgi: take HTTP_HOST from the routed host only. Pull request #8355
- Fastcgi: rewrite to index.php only if it exists. Pull request #8372
- Fastcgi: split script path at segment boundary. Pull request #8386
- Fileserver: reject regular files addressed with a trailing separator. Pull request #8379
- Fileserver: apply slash rules to the fallback entry. Pull request #8387
- Caddyfile: reject site blocks with unbalanced braces. Pull request #8375
- Httpcaddyfile: reject conflicting
client_authwhen merging TLS policies. Pull request #8306 - Reverseproxy: skip unavailable upstream with a single
weighted_round_robinweight. Pull request #8320
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.
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
- The
php_fastcgidirectory redirect now stays on the same origin, closing a case where crafted encoded paths produced scheme-relative redirects to an attacker's domain. Pull request #8285 - The file matcher no longer matches a regular file when the candidate path ends in a slash, so paths like /.env/./ no longer resolve to a dotfile. Pull request #8326
- The rewrite handler now escapes the file matcher remainder before the rewritten URI is parsed. Pull request #8325
- The fileserver hides the data directory when it resolves to the relative path./caddy because neither XDG_DATA_HOME nor HOME is set. Pull request #8327
- Basic_auth now checks username uniqueness after {env.*} placeholders are expanded, so accounts that collide only after expansion are rejected. Pull request #8315
- Basic_auth and caddy hash-password now look up hash algorithm names among installed hash modules, not just bcrypt and argon2id. Pull request #8063
- Copy_response_headers now strips hop-by-hop headers such as Alt-Svc, Keep-Alive and Proxy-Authenticate when copying upstream response headers. Pull request #8270
- The FastCGI transport stops response bodies at the declared Content-Length, so extra bytes from a responder no longer truncate HTTP/1.1 responses or break HTTP/2 connections. Pull request #8212
- ParseNetworkAddress rejects overlong ports instead of building an error message that copies the whole invalid port. Pull request #8277
- The shared SRV and A DNS discovery caches are now keyed by resolver as well as record, so upstreams using different resolvers no longer share entries. Pull request #8252
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
- Encode: use httpguts to look for Accept-Encoding in Vary Pull request #8329
- Admin: handle Cache-Control directives with httpguts so reloads are not skipped Pull request #8330
- Fileserver: hide the data directory when it is relative Pull request #8327
- Fileserver: don't match a regular file when the path ends in a slash Pull request #8326
- Rewrite: escape the file matcher remainder before rewriting Pull request #8325
- Caddyauth: check
basic_authusername uniqueness after placeholder expansion Pull request #8315 - Caddyauth: support third-party hash modules in
basic_authand hash-password Pull request #8063 - Core: reject overlong ports in ParseNetworkAddress Pull request #8277
- Reverseproxy: strip hop-by-hop headers when copying response headers Pull request #8270
- Fastcgi: stop response bodies at the declared Content-Length Pull request #8212
- Reverseproxy: make the shared DNS discovery cache resolver-aware Pull request #8252
- Fastcgi: keep the
php_fastcgidirectory redirect on the same origin Pull request #8285
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
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
- The tls matcher can now be used inside expression matchers through a CEL implementation. Pull request #8088
- The reverse proxy emits OpenTelemetry client spans for upstream requests when telemetry is configured. Pull request #8177
- The reverse proxy preserves request trailer values by syncing the outbound trailer map when the incoming body reaches EOF. Pull request #8246
- File placeholder replacements are cached and capped at 1000 unique files to avoid timeouts on large numbers of repeated lookups. Pull request #8248
- Windows service status updates are serialised so a service no longer stays in START_PENDING after Caddy begins serving traffic. Pull request #8274
- The reverse proxy closes the backend body and hijacked socket when upgrade setup fails before the tunnel starts. Pull request #8269
- The reverse proxy strips hop-by-hop headers from 1xx interim responses such as 103 Early Hints. Pull request #8256
- The reverse proxy retries dial errors wrapped by a forward proxy instead of returning 502 for non-GET requests. Pull request #8264
- Privileged binds are retried on EACCES instead of relying on a hardcoded check for ports below 1024. Pull request #8253
- Client certificate verifiers are skipped when no certificate is presented, so request and
verify_if_givenmodes accept clients without one. Pull request #8251
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
- Caddyhttp: add CEL expression support to the tls matcher Pull request #8088
- Reverseproxy: emit OpenTelemetry client spans Pull request #8177
- Reverseproxy: preserve request trailer values Pull request #8246
- Replacer: cache file lookups and cap them Pull request #8248
- Windows: serialise service status updates Pull request #8274
- Reverseproxy: close backend body and hijacked socket on upgrade setup failures Pull request #8269
- Reverseproxy: strip hop-by-hop headers from interim responses Pull request #8256
- Reverseproxy: retry dial errors wrapped by a forward proxy Pull request #8264
- Core: retry privileged binds on EACCES instead of checking port < 1024 Pull request #8253
- Caddytls: skip client cert verifiers when no certificate is presented Pull request #8251
- Templates: use the earliest front matter closing fence Pull request #8259
- Logging: parse request URIs in the query filter like the server does Pull request #8255
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.
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
- Reverted the reverseproxy change that honored health check redirect destinations, because a backend-controlled cross-origin redirect could send custom secrets or TLS client credentials outside the original upstream. Pull request #8242
- Added experimental WebTransport passthrough to the reverse proxy, using HTTP/3 Extended CONNECT with the webtransport protocol. Pull request #7669
- Fixed reverseproxy dropping read errors with unlimited buffers, so a body cut short by
request_bodymax_sizenow returns 413 instead of forwarding a truncated length with 200. Pull request #8207 - Headers now evaluate conditional defaults independently, so one field already on the response no longer stops every default in the block and matchers apply to those fields. Pull request #8217
- Fixed logging
dir_modefrom_fileso directories derive from the 0600 file mode and get 0700, instead of being created as 0200 and failing to open the log file. Pull request #8225 - Hash-password now accepts piped input without a final newline and drops trailing CRLF, so Windows line endings are no longer hashed as part of the password. Pull request #8227
- FastCGI responses with a Location header and no Status header now use 302 Found, matching RFC 3875, net/http/cgi and nginx. Pull request #8209
- TLS policies are now cloned per listener, so a site block spanning several listener addresses no longer lets a later server rewrite an earlier server's policy. Pull request #8192
- Directory browsing now returns an empty listing for offsets past the end of pagination instead of returning the first page again. Pull request #8213
- Added a
log_leveldirective for access logs so the severity can be overridden for matching requests. Pull request #8201
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
- Reverseproxy: reverted honoring health check redirect destinations to avoid sending credentials off the original upstream Pull request #8242
- Reverseproxy: added experimental WebTransport passthrough over HTTP/3 Extended CONNECT Pull request #7669
- Reverseproxy: no longer drops read errors with unlimited buffers; truncated bodies return 413 Pull request #8207
- Headers: conditional defaults are evaluated independently and respect match Pull request #8217
- Logging:
dir_modefrom_filenow creates directories as 0700 Pull request #8225 - Caddyauth: hash-password accepts input without a final newline and drops trailing CRLF Pull request #8227
- Fastcgi: a Location response without Status uses 302 Pull request #8209
- Httpcaddyfile: TLS policies are isolated across listeners Pull request #8192
- Fileserver: offsets past the end return an empty listing Pull request #8213
- Httpcaddyfile: added
log_leveldirective for access logs Pull request #8201 - Templates: avoid zero content length for bodyless responses Pull request #8153
- Logging: module logs are included from the parent namespace Pull request #8221
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
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
- Retries for expression based
lb_retry_matchnow only apply when the expression actually inspects response data, so request only conditions no longer cause extra upstream attempts. Pull request #8168 - Routes in a satisfied group no longer run their matchers, avoiding matcher errors and other side effects from routes whose result was already ignored. Pull request #8189
- Headers set before proxying, such as those from the header directive, survive upstream informational responses like 103 Early Hints. Pull request #8169
- Repeated expression matchers inside one named matcher or not block are now rejected by the Caddyfile parser instead of being silently dropped. Pull request #8183
- Expired request body read deadlines are now preserved so a timed out HTTP/1 upload no longer blocks net/http while draining the remaining body. Pull request #8178
- HEAD responses from the encode handler no longer include an empty compressed stream trailer as Content-Length. Pull request #8150
- Host matching for
logger_namesis now case insensitive, so access logs for hosts with different casing reach the configured logger instead of stderr. Pull request #8176 - Weighted round robin no longer panics when fewer weights than upstreams are configured and an earlier upstream is down. Pull request #8159
- Random_choose with all hosts busy now picks the least loaded host instead of choosing between the most and least loaded. Pull request #8160
- Path qualified
file_serverhide rules now also apply to browse entries and precompressed sidecars. Pull request #8155
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
- Reverseproxy: only retry on expression based
lb_retry_matchwhen the expression uses response data Pull request #8168 - Caddyhttp: skip matchers for routes in a satisfied route group Pull request #8189
- Reverseproxy: keep own headers after 1xx informational responses Pull request #8169
- Caddyhttp: reject repeated expression matchers in a matcher set Pull request #8183
- Caddyhttp: preserve expired request body read deadlines Pull request #8178
- Encode: do not write an empty encoded stream for HEAD responses Pull request #8150
- Caddyhttp: ignore case when matching hosts in
logger_namesPull request #8176 - Reverseproxy: avoid panic in
weighted_round_robinwith fewer weights than upstreams Pull request #8159 - Reverseproxy: pick the least loaded host in
random_choosewhen all are busy Pull request #8160 - Fileserver: apply hide rules to browse entries and precompressed sidecars Pull request #8155
- Fastcgi: classify dial failures for retry Pull request #8172
- Caddyfile: surface OS error when an import file is inaccessible Pull request #8163
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.
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
- V2.11.7 patch release fixes regressions from 2.11.6 including HTTP/2 proxying crashes and streams cut off after a minute, plus adds RFC 10036 Incremental header support. Release
- Route-level timeouts now take precedence over server-wide idle timeouts instead of being silently overridden. Pull request #8121
- Request body timeout deadlines are now revoked when their handler returns, preventing reads from using response controllers after handler completion. Pull request #8107
- Reverse proxy can now optionally detach long-lived upgraded streams from config lifecycle to reduce memory pressure across reloads. Pull request #7649
- Reverse proxy fixes data races when stream detachment fails by not running upgraded tunnels in goroutines after handler returns. Pull request #8139
- File server now returns 404 instead of 400 for requests to paths below regular files like /index.php/foo. Pull request #8131
- Headers handler now preserves multiple Set-Cookie values as separate response fields instead of combining them. Pull request #8080
- New {time.now.rfc3339} placeholder formats current time using RFC 3339 layout with UTC or signed numeric offset. Pull request #8140
- TLS handshake matching gains a not matcher to negate matcher sets, matching HTTP matcher behavior. Pull request #8138
- Caddy on Linux now raises CAP_NET_BIND_SERVICE when binding privileged ports below 1024. Pull request #8102
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
- V2.11.7 released: fixes HTTP/2 proxying crash and stream timeout regressions; adds RFC 10036 Incremental header Release
- Timeouts: route-level timeouts now take precedence over server-wide idle timeouts Pull request #8121
- HTTP: request body deadline ownership ends with handler completion Pull request #8107
- Reverse proxy: fixes data races when stream detachment fails Pull request #8139
- File server: requests to paths below files return 404 instead of 400 Pull request #8131
- Headers: Set-Cookie values remain separate instead of being combined Pull request #8080
- Core: adds {time.now.rfc3339} placeholder for RFC 3339 time formatting Pull request #8140
- TLS: adds not matcher for negating handshake matcher sets Pull request #8138
- Reverse proxy: upgraded streams can optionally detach from config lifecycle Pull request #7649
- TLS: repeated matchers in nested matcher sets are now preserved Pull request #8137
- Listeners: Unix sockets immediately close and unlink on reload Pull request #8061
- Build: minimum Go version raised to 1.26 Pull request #8056
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.
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
- Reverse_proxy with HTTP/3 now respects
tls_trust_poolinstead of silently ignoring custom CAs and verifying against system roots. Pull request #8042 - Map directive now allows the same input text for both literal and regexp rules, storing them in separate fields as intended. Pull request #8067
- Caddyauth basic auth provider now only replaces known placeholders in usernames and passwords, preserving literal braces in credentials. Pull request #8017
- Request_body set directive now only replaces known placeholders, preventing JSON bodies from being mangled or emptied. Pull request #8008
- Caddyhttp now surfaces 413 status when request body placeholders exceed
max_sizelimit instead of silently failing. Pull request #7969 - Admin /load API now returns 400 Bad Request for invalid Caddyfiles with warnings instead of incorrectly returning 200 OK. Pull request #7267
- Reverseproxy now flushes partial responses to clients instead of buffering them. Pull request #7849
- Websocket header normalization moved later in processing to prevent rewriting by cloneRequest and other operations. Pull request #7921
- Caddyhttp fixed off-by-one error in MaxSizeSubjectsListForLog that leaked one domain into output when maxToDisplay was 0. Pull request #7970
- Fastcgi now explains why 411 responses occur for requests with unknown-length bodies like chunked or HTTP/2 without content-length. Pull request #7956
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
- Reverse_proxy with HTTP/3 now respects
tls_trust_poolconfiguration Pull request #8042 - Map directive allows same input text for literal and regexp rules Pull request #8067
- Caddyauth basic auth only replaces known placeholders in credentials Pull request #8017
- Request_body set only replaces known placeholders, preserving JSON structure Pull request #8008
- Request_body
max_sizelimit now surfaces 413 status via placeholders Pull request #7969 - Admin /load API returns 400 for invalid Caddyfiles with warnings Pull request #7267
- Reverseproxy flushes partial responses to clients Pull request #7849
- Websocket header normalization moved later to prevent unwanted rewrites Pull request #7921
- Caddyhttp fixed MaxSizeSubjectsListForLog off-by-one error Pull request #7970
- Caddyhttp randString sameCase dictionary corrected to exclude '0' Pull request #7972
- Fastcgi explains 411 responses for unknown-length request bodies Pull request #7956
- Removed AI moderator workflow Pull request #8059
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.
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.