dyhkwongExclave 代码贡献者

值得推荐作者发言

GitHub·2026.09.22 19:06:56（UTC+8）

dyhkwong：Exclave 将按 ALPN 兼容性中断调整既有配置、新建配置与内核行为

在跟踪 V2Ray QUIC 传输 ALPN 兼容性中断的议题中，dyhkwong 列出 Exclave 需要的改动：既有配置把「无 ALPN」改写为 ALPN h2 与 http/1.1；新建配置中「无 ALPN」表示 ALPN h3；exclave-core 目前接受 h3、h2 或 http/1.1 之一（他注明这暂不具备抗主动探测能力），未来版本起只接受 h3；Shadowsocks v2ray-plugin 短期内不太可能更新，Exclave 对其始终使用 ALPN h2 与 http/1.1；分享链接始终带上 ALPN 参数，以避免隐式和含糊的默认值。

作者原文@dyhkwong

So Exclave needs the following changes:

• For existing profiles in Exclave, rewrite "no ALPN" into ALPN "h2" and "http/1.1".
• For newly created profiles in Exclave, "no ALPN" means ALPN "h3".
• For exclave-core, accepts one of ALPN "h3", "h2" or "http/1.1" for now (not active-probing resistant). Starting from a future version, only accepts ALPN "h3".
• It is unlikely for Shadowsocks v2ray-plugin to receive an update in the near future. Exclave has to always use ALPN "h2" and "http/1.1" for Shadowsocks v2ray-plugin.
• For share link, always add the ALPN parameter to avoid implicit and ambiguous default values.

What a drama.