v0.29.4

docs/CACHE.md

@@ -20,6 +20,22 @@ refresh while keeping directive-controlled stale delivery through RFC 5861 and r
 validator-based handling of response `no-cache` instead of reproducing Varnish hit-for-miss
 behavior exactly.
 
+## Web Server origins (0.29.4)
+
+A Web Service selected as the vhost source now uses the normal RustProxy shared
+object-cache pipeline when both global and vhost cache policy permit it.
+`Cache-Control: public, max-age=...` (or another eligible freshness policy)
+can produce `MISS` followed by `HIT` instead of a browser-only cache header.
+Vhost response rules run before cache fill, and transformed output is what is
+stored. Private/`Set-Cookie`/`no-store` origin responses remain ineligible,
+even if a later response-header rule replaces their visible cache headers.
+
+For Web Server sources, stale entries are refreshed by a new local-source
+request rather than the remote-backend revalidation worker. As with reverse
+proxy origins, range requests and conditional requests can reuse fresh stored
+representations. Do not rely on stale-if-error remote-backend refresh behavior
+for local Web Server routes.
+
 ## Settings
 
 | Field | Default | Bounds / meaning |