Repository navigation
XDRIVE transport: Support h3 (Chrome CH by default) and XMUX as well; Send Chrome HTTP headers (User-Agent, etc.) by default - #7187
Conversation
|
感觉这个 PR 最好配合 #7135 , 所以 h3 时默认 maxConnections 是 1? |
ca0b119 to
3fdaf41
Compare
|
UA 目前是什么情况 |
|
另外你的下一个 PR 会是 #7170 (comment) 吗,保留 @Ahmad-2213 的 commits、author 等信息就行 |
|
Greetings; I'm glad you find it useful. |
|
@RPRX none was set, so after a hello of chrome google got Go-http-client/2.0 over h2 and quic-go HTTP/3 over h3. added a commit: xdrive now takes the headers that xhttp and doh take, chrome's by default, and a template can set its own User-Agent in headers or one of chrome, firefox, safari, edge, curl, golang yes, after this one. his main has about 70 xdrive commits on a base from before #7181, and @Ahmad-2213 says to take the final version of the folder, so I'll bring that onto main with him as co-author on the commits, without mux resume, which is a separate thing |
|
@4RH1T3CT0R7 那你先准备一下吧,明天会合并这两个 PR, |
|
ok, I'll prepare it on top of these two. yes, I test on a drive account of my own, the numbers in this pr are from it |
|
关于 XDRIVE 的 XMUX:h3 默认 maxConnections 1,h2 在 Google Drive 上暂时默认为 4,等 TSPU/NIN 针对它了再做调整
同样支持 XMUX 的 XHTTP、MASQUE 用的是 x/net #6797 (comment) ,XDRIVE 直接用的 Go HTTP, |
as RPRX asked in #7181. xmux the way masque has it, maxConnections 4 on google drive over h2 and 1 otherwise by default: a session takes a connection of xmux and moves to another after hMaxRequestTimes or hMaxReusableSecs, and the old one closes once its requests end. and h3 with alpn ["h3"] like DoH: quicParams and udp masks from finalmask, chrome parrot, bbr by default like xhttp, no fallback to h2 for now, with google-drive only noise among the udp masks
from a VPS to googleapis with 150 ms added, 32 parallel 4 MiB puts: google gives an h2 connection 1 MiB of window, so on one connection they make 3.4 MiB/s, spread over 4 connections 9-11, and one h3 connection makes 16.5, so h3 takes one by default