@@ -63,7 +63,7 @@ Fluxheim is licensed under the European Union Public Licence 1.2.
6363| Regex path rewrite templates | ✅ | ` 1.4.1 ` ; ` rewrite_template ` maps regex routes to safe upstream paths without nginx-style rewrite loops or ` if ` . |
6464| Method-based routing | ✅ | ` 1.4.1 ` ; optional route ` methods = ["GET", "HEAD"] ` filters. |
6565| HTTPS redirects | ✅ | Optional global HTTP-to-HTTPS redirects with safe Host validation. |
66- | Secure headers | ✅ | Request/response policy, opt-in hardening and cross-origin-isolation profiles, typed CSP reporting and modern browser controls, validated request-aware CORS, automatic ` Vary ` , and bounded ` Retry-After ` ; origin ` Server ` headers are preserved by default and removed by the hardening profiles. |
66+ | Secure headers | ✅ | Request/response policy, opt-in hardening and cross-origin-isolation profiles, typed CSP reporting and modern browser controls, validated request-aware CORS, automatic ` Vary ` , bounded ` Retry-After ` , and opt-in RFC 9211/9209/9530 response metadata ; origin ` Server ` headers are preserved by default and removed by the hardening profiles. |
6767| PHP-FPM applications | ✅ | External php-fpm for existing pools. |
6868| Managed PHP-FPM | ✅ | Fluxheim-supervised php-fpm pools for zero-admin WordPress-style deployments. |
6969
@@ -352,8 +352,8 @@ Release tags use the same profile/OS suffixes on both registries. The first
352352` 1.7.x ` image tags include ` v1.7.0-wolfi ` , ` v1.7.0-cache-wolfi ` ,
353353` v1.7.0-proxy-wolfi ` , ` v1.7.0-load-balancer-wolfi ` , and ` v1.7.0-php-wolfi ` ;
354354follow-up ` 1.7.x ` releases use the same suffix pattern, for example
355- ` v1.7.11 -wolfi ` , ` v1.7.11 -cache-wolfi ` , ` v1.7.11 -proxy-wolfi ` ,
356- ` v1.7.11 -load-balancer-wolfi ` , and ` v1.7.11 -php-wolfi ` .
355+ ` v1.7.12 -wolfi ` , ` v1.7.12 -cache-wolfi ` , ` v1.7.12 -proxy-wolfi ` ,
356+ ` v1.7.12 -load-balancer-wolfi ` , and ` v1.7.12 -php-wolfi ` .
357357
358358Release note for ` 1.5.15 ` : the signed git tag ` v1.5.15 ` is the canonical code
359359tag. The GitHub Release page is published under ` v1.5.15-release ` because the
@@ -424,13 +424,14 @@ scripts/validate-features.sh proxy,web,tls-rustls,load-balancer
424424
425425</details >
426426
427- ## Current Release: 1.7.11 Zero-Downtime Upgrades
427+ ## Current Release: 1.7.12 Standards Metadata And FIPS Evidence
428428
429429Fluxheim does not treat every planned idea as stable. The current release line
430- is ` 1.7.11 ` , the zero-downtime process-upgrade release after the stable
431- ` 1.7.0 ` through ` 1.7.10 ` Wasm milestones. It adds bounded drain, strict
432- systemd listener inheritance, readiness-gated native handoff, and a tested
433- Podman blue/green pattern behind a stable fronting listener.
430+ is ` 1.7.12 ` , the standards-based response-metadata and reproducible
431+ FIPS-backend evidence release after the stable Wasm and zero-downtime
432+ milestones. It adds opt-in RFC 9211 ` Cache-Status ` , low-cardinality RFC 9209
433+ ` Proxy-Status ` , RFC 9530 response digests, and pinned proof environments that
434+ build and execute the OpenSSL-FIPS and rustls/AWS-LC-FIPS profiles.
434435
435436- ` 1.0 ` is the gateway foundation: vhosts, routes, redirects, static serving,
436437 proxying, SNI/TLS, safe ACME challenge exceptions, systemd/RPM packaging, and
@@ -494,6 +495,13 @@ Podman blue/green pattern behind a stable fronting listener.
494495 closes the native HTTP/1 parser audit with validated-only request heads,
495496 bounded fragmentation-independent chunk decoding, strict request-target and
496497 authority handling, and ownership-safe critical background supervision.
498+ - ` 1.7.12 ` adds response metadata generated from real runtime outcomes and
499+ final response bytes. Cache and proxy status fields remain opt-in and avoid
500+ backend topology or arbitrary error strings; digest behavior is live-tested
501+ across cache, compression, conditional, ` HEAD ` , and range responses. Pinned
502+ CI-only proof environments build and run both FIPS-capable TLS profiles and
503+ capture provider, toolchain, dependency, binary, and image evidence. They are
504+ not published FIPS images or a claim that Fluxheim itself is FIPS validated.
497505
498506Detailed cache behavior, config examples, operational limits, and smoke-test
499507coverage are documented in [ Cache Backends] ( docs/cache-backends.md ) ,
0 commit comments