@@ -40,6 +40,15 @@ HTTP/2 CONNECT presented to the public origin is always treated as cover,
4040including when it carries an otherwise valid ticket: the handler removes
4141` Proxy-Authorization ` before delegation and never dials its authority.
4242
43+ Public physical-connection limits are separate from authenticated tunnel-stream
44+ limits, and the combined TCP/UDP server shares its global and per-source
45+ connection allowance. Source builds after v1.0.1 reject an excess H3 connection
46+ with ` H3_EXCESSIVE_LOAD ` (` 0x107 ` ), rather than reusing the native relay's code,
47+ which means ` H3_INTERNAL_ERROR ` in [ HTTP/3] ( https://www.rfc-editor.org/rfc/rfc9114.html#section-8.1 ) .
48+ Rejection happens before HTTP dispatch;
49+ the existing admitted connection remains usable and closing it releases capacity.
50+ This is overload handling, not a tunnel authentication response.
51+
4352### Website WebSocket support in source builds
4453
4554Source builds after v1.0.1 also forward valid HTTP/1.1 WebSocket upgrades to
@@ -202,6 +211,17 @@ the upstream cannot be reached. Consequently, an upstream that requires an
202211` Authorization ` request header is not suitable without a separate authorized
203212front end.
204213
214+ Source builds after v1.0.1 disable automatic compression negotiation and response
215+ decompression on the proxy's private default upstream transport. The visitor's
216+ ` Accept-Encoding ` remains unchanged: explicitly requested gzip still works, and
217+ the origin's encoded bytes, ` Content-Encoding ` , length, digest and ETag remain
218+ together. This avoids rewriting ` no-transform ` content while retaining metadata
219+ for the old bytes; see [ HTTP message transformations] ( https://www.rfc-editor.org/rfc/rfc9110.html#section-7.7 ) .
220+ It does not verify the website's digest or establish browser-like fingerprints.
221+ Applications supplying a custom RoundTripper retain their own negotiation/decoding
222+ policy and must configure transparent forwarding themselves. Static cover,
223+ authenticated tunnel payloads and the published v1.0.1 binary are unchanged.
224+
205225#### Optional fixed public origin in source builds
206226
207227Source builds after v1.0.1 can separate the website's public HTTP identity
0 commit comments