v0.8.1

Bugfix: Correct Legacy Header Name for gregjones/httpcache Compatibility

This patch release corrects the legacy header name used for compatibility with gregjones/httpcache. The previous release incorrectly used X-Cache-Status; this has been fixed to use the correct legacy header, X-From-Cache.

Highlights

• Legacy Header Correction

  • The legacy header for compatibility is now correctly set as X-From-Cache, matching the behavior of gregjones/httpcache.

  • Header Value Mapping:

    X-Httpcache-Status	X-From-Cache	Description
    HIT	1	Served from cache
    STALE	1	Served from cache but stale
    REVALIDATED	1	Revalidated with origin
    MISS	(not set)	Served from origin
    BYPASS	(not set)	Bypassed cache, served from origin

    X-Httpcache-Status is set on every response, while X-From-Cache is only set for cache hits, stale, or revalidated responses.

  • Example response headers for a stale cache hit:

    X-Httpcache-Status: STALE
    X-From-Cache: 1

• No other changes were made in this release.

Full Changelog: v0.8.0...v0.8.1

---

Migration Note:
X-From-Cache is provided for compatibility and may be removed in a future major release. Please migrate to X-Httpcache-Status for continued support and improvements.

---

Call for Feedback

The project is nearing a stable v1.0.0 milestone.
Any further feedback, issues, or contributions are welcome as we finalize the implementation and documentation.