v0.3.0-beta

Spooky 0.3.0-beta — HTTP/1.1 Upstream Support

Minor release covering all changes since 0.2.1-beta.

Added

• HTTP/1.1 upstream transport — http:// backends are now forwarded over a pooled HTTP/1.1 connection. No backend changes required; use http://host:port in your config and Spooky selects the right transport automatically.
• Scheme-aware dispatch — backend URL scheme determines transport: https:// backends use HTTP/2, http:// backends use HTTP/1.1. Mixed deployments are supported within the same upstream pool.
• DNS refresh for H1 backends — when backend hostnames re-resolve, HTTP/1.1 pooled connections rotate alongside HTTP/2 connections.
• H1 health checks — active health probes now use the same transport as the target backend scheme.
• TE: trailers header forwarded on H1 upstream requests to preserve trailer semantics.

Fixed

• Config validator no longer rejects http:// upstreams due to unused TLS CA path checks — HTTP-only configs boot cleanly without requiring any TLS material for those backends.

Known Limitations

• No dynamic backend discovery (static config only)
• No configuration hot reload (restart to apply config changes)
• Pre-GA — extended soak testing recommended before broad production rollout