github
/
Xray-docs-next
mirror of https://github.com/XTLS/Xray-docs-next
1
0
Fork 0
Code Issues Releases Wiki Activity

also update splithttp english docs with changes from main

pull/527/head
mmmray 2024-07-04 15:53:00 -05:00
parent 66382b4845
commit 2e4bbb7496
1 changed files with 9 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
docs/en/config/transports/splithttp.md
View File

@ -5,9 +5,9 @@ Uses HTTP chunked-transfer encoding for download, and multiple HTTP requests for
Can be deployed on CDNs that do not support WebSocket, but there is still one requirement: Can be deployed on CDNs that do not support WebSocket, but there is still one requirement:
**The CDN must support HTTP chunked transfer encoding in a streaming fashion**, **The CDN must support HTTP chunked transfer encoding in a streaming fashion**,
no response buffering. The transport will send the `X-Accel-Buffering: no` no response buffering. The transport will send the `X-Accel-Buffering: no` and
response header, but only some CDNs respect this. If the connection hangs, most `Content-Type: text/event-stream` response headers, but only some CDNs respect this.
likely this part does not work. If the connection hangs, most likely this part does not work.
This transport serves the same purpose as Meek (support non-WS CDN). It has the This transport serves the same purpose as Meek (support non-WS CDN). It has the
above streaming requirement to the CDN so that download can be much faster than above streaming requirement to the CDN so that download can be much faster than
@ -102,9 +102,11 @@ Recommendations:
expected that the CDN will translate arbitrarily between versions. A HTTP/1.1 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. server may indirectly end up talking to a h2 client, and vice versa.
The SplitHTTP client in Xray does not support HTTP/1.1 over TLS. If TLS is In order to keep the implementation simple, SplitHTTP client in Xray assumes
enabled, h2 prior knowledge is assumed. The supported combinations are h2 prior knowledge if TLS is enabled. HTTP/1.1 has to be enabled explicitly
therefore HTTP/1.1 without TLS, and h2 with TLS. by setting `http/1.1` ALPN. h2c is not supported on the client at all.
The SplitHTTP server in Xray supports all common combinations as expected: The SplitHTTP server in Xray supports all common combinations as expected:
HTTP/1.1 with or without TLS, and h2 with TLS. HTTP/1.1 with or without TLS, h2 and h2c, however no h3.
Neither Xray server nor client support h3, but this may change in the future.