Codsi HTTP/3 wuxuu u baahan yahay waddo proxy UDP qaadi karta
Kala sooc gaadiidka QUIC ee HTTP/3 iyo tunnellada TCP ee HTTP CONNECT caadiga ah iyo taageerada UDP ee ikhtiyaariga ah ee adeegga SOCKS5.
Macmiil si guul leh u gaara HTTPS isagoo maraya proxy TCP ma uusan samayn waddo HTTP/3. HTTP/3 waxay isticmaashaa QUIC, QUICna waxay isticmaashaa UDP.
Tunnel-ka caadiga ah ee HTTP CONNECT wuxuu bixiyaa qulqul TCP ilaa ujeeddadiisa. Ma noqdo gudbiye UDP marka URL-ku ku bilaabmo HTTPS ama ujeeddadu ay dhageysato port 443.
SOCKS5 sidoo kale wuxuu u baahan yahay waddada UDP
SOCKS5 waxay qeexdaa isku-xirka UDP, laakiin macmiilka iyo serverka labaduba waa inay fuliyaan, iyo barta gudbinta waa in la gaari karo. Maktabadda bixisa kaliya dialer TCP SOCKS ma bixin karto gaadiid datagram sababtoo ah magaca noocaheeda wuxuu leeyahay SOCKS5.
Si la mid ah, qayb ka mid ah qalabka oo la yiraahdo proxy waxay noqon kartaa jilitaanka luminta xirmooyinka horumarinta halkii ay ahaan lahayd macmiil proxy sare oo guud. Baadh interface-keeda dhabta ah iyo gaadiidka la taageeray.
Heerarka sida CONNECT-UDP waxay qeexaan dariiq kale oo UDP lagu qaado nidaamka proxy HTTP. Waxay u baahan yihiin taageero labada dhinac waana in aan lagu khaldin CONNECT dhaqameed.
Haddii macmiilka HTTP uu dib ugu laabto HTTP/2 ama HTTP/1.1 TCP, codsigu wuxuu ku guulaysan karaa proxy-ga caadiga ah isagoo aan la isticmaalin xiriir HTTP/3. Diiwaangeli borotokoolka la wada hadlay marka farqigaas uu muhiim yahay.
Sidaas darteed su'aasha is-waafajinta faa'iidada leh waa mid gaar ah: macmiilkan ma ku qaadi karaa datagram-ka QUIC proxy-kan isagoo isticmaalaya habkan la taageeray? Bog browser shaqeeya ama hubinta port TCP ayaa ka jawaaba su'aal yar.