diff --git a/changelog.md b/changelog.md index 9bc711d..be71c88 100644 --- a/changelog.md +++ b/changelog.md @@ -1,5 +1,11 @@ # Changelog +## 2026-03-20 - 25.17.7 - fix(readme) +document QUIC and HTTP/3 compatibility caveats + +- Add notes explaining that GREASE frames are disabled on both server and client HTTP/3 paths to avoid interoperability issues +- Document that the current HTTP/3 stack depends on pre-1.0 h3 ecosystem components and may still have rough edges + ## 2026-03-20 - 25.17.6 - fix(rustproxy-http) disable HTTP/3 GREASE for client and server connections diff --git a/readme.md b/readme.md index 63fb979..d1c3c1b 100644 --- a/readme.md +++ b/readme.md @@ -1111,6 +1111,10 @@ SmartProxy searches for the Rust binary in this order: 5. Local dev build (`./rust/target/release/rustproxy`) 6. System PATH (`rustproxy`) +### QUIC / HTTP3 Caveats +- **GREASE frames are disabled.** The underlying h3 crate sends [GREASE frames](https://www.rfc-editor.org/rfc/rfc9114.html#frame-reserved) by default to test protocol extensibility. However, some HTTP/3 clients and servers don't properly ignore unknown frame types, causing 400/500 errors or stream hangs ([h3#206](https://github.com/hyperium/h3/issues/206)). SmartProxy disables GREASE on both the server side (for incoming H3 requests) and the client side (for H3 backend connections) to maximize compatibility. +- **HTTP/3 is pre-release.** The h3 ecosystem (h3 0.0.8, h3-quinn 0.0.10, quinn 0.11) is still pre-1.0. Expect rough edges. + ### Performance Tuning - ✅ Use NFTables forwarding for high-traffic routes (Linux only) - ✅ Enable connection keep-alive where appropriate diff --git a/ts/00_commitinfo_data.ts b/ts/00_commitinfo_data.ts index fce79e6..4391545 100644 --- a/ts/00_commitinfo_data.ts +++ b/ts/00_commitinfo_data.ts @@ -3,6 +3,6 @@ */ export const commitinfo = { name: '@push.rocks/smartproxy', - version: '25.17.6', + version: '25.17.7', description: 'A powerful proxy package with unified route-based configuration for high traffic management. Features include SSL/TLS support, flexible routing patterns, WebSocket handling, advanced security options, and automatic ACME certificate management.' }