kwanan nan da IETF (Internet Engineering Task Force), wanda ke haɓaka ka'idoji da gine-ginen Intanet, sanar dashi labarai cewa kammala samar da RFC don ka'idar HTTP/3.0 kuma an buga ƙayyadaddun bayanai masu alaƙa a ƙarƙashin masu gano RFC 9114 da RFC 9204.
Bayanin HTTP/3.0 ya sami matsayi na "Proposed Standard", bayan haka aikin zai fara baiwa RFC matsayin daftarin ma'auni (Draft Standard), wanda a zahiri yana nufin cikakken daidaita ka'idar tare da la'akari da duk maganganun da aka yi.
Protocol HTTP/3 yana bayyana amfani da ƙa'idar QUIC (Haɗin Intanet mai sauri na UDP) a matsayin sufuri don HTTP/2. QUIC plugin ne zuwa ka'idar UDP wanda ke goyan bayan haɓakar haɗin kai da yawa kuma yana ba da hanyoyin ɓoyewa daidai da TLS/SSL.
Google ne ya kirkiro wannan yarjejeniya a cikin 2013 a matsayin madadin TCP + TLS don Yanar Gizo, magance matsalar saitin haɗin haɗin gwiwa mai tsawo da lokacin tattaunawa a cikin TCP da kuma kawar da jinkiri saboda asarar fakiti yayin canja wurin bayanai.
A halin yanzu, An riga an aiwatar da tallafin QUIC da HTTP/3.0 a duk masu bincike shahararrun gidajen yanar gizo. A gefen uwar garke, ana samun aiwatar da HTTP / 3 don nginx (a cikin reshe daban kuma a matsayin wani nau'i daban), Caddy , IIS da LiteSpeed . HTTP/3 kuma yana samun goyan bayan Cibiyar Isar da Abun ciki ta Cloudflare.
Babban fasali na QUIC:
- Babban tsaro, kama da TLS (a zahiri, QUIC yana ba da ikon amfani da TLS akan UDP)
- Gudanar da amincin watsawa don hana asarar fakiti
- Ikon kafa haɗin kai nan take da kuma tabbatar da ɗan jinkiri tsakanin aika buƙatu da karɓar amsa (RTT, lokacin tafiya zagaye)
- Yi amfani da lambar jeri daban-daban lokacin da ake sake aikawa da fakiti, yana ba ku damar guje wa rashin fahimta lokacin tantance fakitin da aka karɓa da kuma kawar da ɓata lokaci.
- Rasa fakiti yana shafar isarwar rafin da ke tattare da shi kuma baya dakatar da isar da bayanai a cikin rafukan da aka watsa a layi daya akan haɗin yanzu
- Kuskuren kayan aikin gyara waɗanda ke rage jinkiri saboda sake watsa fakitin da suka ɓace. Amfani da lambobin gyara kuskuren matakin fakiti na musamman don rage yanayin da ke buƙatar sake watsa bayanan fakitin da suka ɓace.
- Iyakokin toshe bayanan sirri sun daidaita tare da iyakokin fakitin QUIC, rage tasirin asarar fakiti kan yanke abun ciki na fakiti masu zuwa.
- Babu matsala tare da toshe layin TCP
- Goyan bayan gano haɗin haɗi don rage lokacin sake haɗawa ga abokan cinikin hannu
- Yiwuwar haɗa ingantattun hanyoyin haɗin gwiwa don sarrafa yawan wuce gona da iri
- Yi amfani da dabarun hasashen bandwidth a kowace hanya don tabbatar da mafi kyawun ƙimar isar da fakiti, guje wa yanayin cunkoso inda fakiti suka ɓace.
- Sanannen aiki da nasarorin aiki akan TCP. Don ayyukan bidiyo kamar YouTube, an nuna QUIC don rage ayyukan buffer na bidiyo da kashi 30%.
Baya ga wannan, kuma a lokaci guda, an buga sabbin sigogin ƙayyadaddun ƙa'idodin HTTP/1.1 (RFC 9112) da HTTP/2.0 (RFC 9113), da kuma takaddun da ke ayyana ma'anar buƙatun HTTP (RFC) 9110) da HTTP caching control headers (RFC 9111).
Na canje-canje a cikin ƙayyadaddun bayanai HTTP/1.1, zaku iya lura da haramcin daga daban-daban amfani da karusa dawo hali (CR) a waje da jiki tare da abun ciki, watau a cikin abubuwan yarjejeniya, ana iya amfani da halin CR kawai tare da sabon layin layi (CRLF).
El An inganta shimfidar tsarin buƙatun buƙatu don sauƙaƙe rarrabuwar filayen da aka haɗe da sassan da rubutun kai. Ƙara jagororin don sarrafa abubuwan da ba su da ma'ana don toshe hare-haren aji na "Buƙatar HTTP Smuggling" waɗanda za su iya kutsawa cikin abubuwan da wasu masu amfani ke bukata a cikin kwarara tsakanin gaba da baya.
Sabuntawa ga ƙayyadaddun bayanai HTTP/2.0 yana bayyana goyan bayan TLS 1.3, tsarin ba da fifiko da filaye masu alaƙa da tsarin sabuntawa An soke haɗin HTTP/1.1 da aka yanke.
A ƙarshe, idan kuna sha'awar samun damar ƙarin sani game da shi, kuna iya tuntuɓar cikakkun bayanai a cikin bin hanyar haɗi.