v0.32.4

docs/TRANSPORT.md

@@ -35,10 +35,13 @@ Extended CONNECT on vhosts that did not opt in. Ordinary CONNECT and other Exten
 protocols remain rejected because RustProxy is not an open forward proxy. RFC 8441 may bridge
 to an HTTP/1.1 WebSocket backend or use a backend explicitly configured for HTTP/2.
 
-HTTP/2 and `auto` upstream configuration require `preserve_host: false` in this
-release. The target URI, pool key and HTTP/2 authority use the configured backend.
-Use HTTP/1.1 for a backend that requires the original Host. The original hostname
-is also available through the proxy-generated `X-Forwarded-Host` field.
+Since 0.32.4, `preserve_host: true` is supported with `http1`, `auto`, `http2`
+and strict `h2`. H1 carries the public Host; on H2 the outgoing `:authority`
+follows that Host. The *network* destination and DNS/ACL policy stay pinned to
+the configured backend URL. TLS SNI and certificate validation independently use
+`tls_server_name` when supplied or the configured origin otherwise.
+The client hostname also remains available via `X-Forwarded-Host`. HTTP health
+probes are separate H1 requests and may need an explicit `health_check.host`.
 
 For ordinary proxy traffic, an explicit `protocol=http2` backend is forwarded with an
 HTTP/2 request version. Cleartext `http://` uses h2 prior knowledge. HTTPS keeps the