From 666a4e0c0c685b67a0b75798ca1a0297a6bc230c Mon Sep 17 00:00:00 2001 From: mmmray <142015632+mmmray@users.noreply.github.com> Date: Fri, 21 Jun 2024 02:50:16 +0200 Subject: [PATCH] Clarify server and client support of h2 in splithttp (#518) --- docs/en/config/transports/splithttp.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/docs/en/config/transports/splithttp.md b/docs/en/config/transports/splithttp.md index 7e70692b5..18bc23aff 100644 --- a/docs/en/config/transports/splithttp.md +++ b/docs/en/config/transports/splithttp.md @@ -100,5 +100,9 @@ Recommendations: expected that the CDN will translate arbitrarily between versions. A HTTP/1.1 server may indirectly end up talking to a h2 client, and vice versa. - SplitHTTP in Xray does not support HTTP/1.1 over TLS. If TLS is enabled, h2 - prior knowledge is assumed. + The SplitHTTP client in Xray does not support HTTP/1.1 over TLS. If TLS is + enabled, h2 prior knowledge is assumed. The supported combinations are + therefore HTTP/1.1 without TLS, and h2 with TLS. + + The SplitHTTP server in Xray supports all common combinations as expected: + HTTP/1.1 with or without TLS, and h2 with TLS.