{"id":52181,"date":"2019-11-02T00:00:00","date_gmt":"2019-11-01T21:00:00","guid":{"rendered":"https:\/\/prohoster.info\/blog\/blog_prohoster\/http-3-razrushenie-osnov-i-divnyj-novyj-mir"},"modified":"2020-02-18T13:59:51","modified_gmt":"2020-02-18T10:59:51","slug":"http-3-razrushenie-osnov-i-divnyj-novyj-mir","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/http-3-razrushenie-osnov-i-divnyj-novyj-mir","title":{"rendered":"HTTP\/3: shkat\u00ebrrimi i themelieve dhe bota e re e mrekullueshme","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p>T\u00eb pakt\u00ebn 20 vjet tani, ne shikojm\u00eb faqe web-i n\u00ebp\u00ebrmjet protokollit HTTP. Shumica e p\u00ebrdoruesve nuk mendojn\u00eb fare se \u00e7far\u00eb \u00ebsht\u00eb dhe si funksionon. T\u00eb tjer\u00ebt e din\u00eb se diku n\u00ebn HTTP ekziston TLS, q\u00eb n\u00ebn t\u00eb ka TCP, n\u00ebn t\u00eb IP dhe k\u00ebshtu me radh\u00eb. Dhe t\u00eb tret\u00ebt \u2013 heretik\u00ebt \u2013 mendojn\u00eb se TCP \u00ebsht\u00eb nj\u00eb gj\u00eb e kaluar, ata duan di\u00e7ka m\u00eb t\u00eb shpejt\u00eb, m\u00eb t\u00eb besueshme dhe m\u00eb t\u00eb mbrojtur. Por n\u00eb p\u00ebrpjekjet e tyre p\u00ebr t\u00eb shpikur nj\u00eb protokoll t\u00eb ri ideal, ata jan\u00eb kthyer tek teknologjit\u00eb e viteve '80 dhe p\u00ebrpiqen t\u00eb nd\u00ebrtosh nj\u00eb bot\u00eb t\u00eb re t\u00eb mrekullueshme mbi to.<br \/>\n<img decoding=\"async\" alt=\"HTTP\/3: shkat\u00ebrrimi i themelieve dhe bota e re e mrekullueshme\" src=\"\/wp-content\/uploads\/2019\/11\/869bd86cc0b47c6c42f315cf20640018.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<h2>Pak histori: HTTP\/1.1<\/h2>\n<p>\nN\u00eb vitin 1997, protokolli i shk\u00ebmbimit t\u00eb informacionit tekstual HTTP versioni 1.1 fitoi RFC-n\u00eb e tij. N\u00eb at\u00eb koh\u00eb, protokolli ishte p\u00ebrdorur nga shfletuesit p\u00ebr disa vjet, dhe standardi i ri zgjati edhe pes\u00ebmb\u00ebdhjet\u00eb vjet. Protokolli punonte vet\u00ebm n\u00eb parimin k\u00ebrkes\u00eb- p\u00ebrgjigje dhe ishte kryesisht i destinuar p\u00ebr shk\u00ebmbimin e informacionit tekstual.<\/p>\n<p>HTTP u projektua p\u00ebr t\u00eb funksionuar mbi protokollin TCP, i cili garanton dor\u00ebzimin e besuesh\u00ebm t\u00eb paketeve deri te destinacioni. Funksionimi i TCP bazohet n\u00eb krijimin dhe mbajtjen e nj\u00eb lidhjeje t\u00eb besueshme midis pikave p\u00ebrfundimtare dhe ndarjen e trafikut n\u00eb segmente. Segmentet kan\u00eb numrin e tyre t\u00eb rendit dhe nj\u00eb kontrollsum\u00eb. N\u00ebse ndonj\u00eb nga segmentet nuk mb\u00ebrrin ose mb\u00ebrrin me nj\u00eb kontrollsum\u00eb t\u00eb gabuar, at\u00ebher\u00eb transmetimi do t\u00eb ndalet derisa t\u00eb rikuperohet segmenti i humbur.<\/p>\n<p>N\u00eb HTTP\/1.0, lidhja TCP mbyllej pas \u00e7do k\u00ebrkese. Kjo ishte jasht\u00ebzakonisht shpenzuese, sepse krijimi i lidhjes TCP (3-Way-Handshake) \u00ebsht\u00eb nj\u00eb proces i ngadalt\u00eb. N\u00eb HTTP\/1.1 u prezantua mekanizmi keep-alive, i cili lejon rip\u00ebrdorimin e nj\u00eb lidhjeje p\u00ebr disa k\u00ebrkesa. Megjithat\u00eb, pasi ajo mund t\u00eb b\u00ebhet shishe qelqi, n\u00eb implementimet e ndryshme HTTP\/1.1 lejohet hapja e disa lidhjeve TCP me nj\u00eb host t\u00eb vet\u00ebm. P\u00ebr shembull, n\u00eb Chrome dhe n\u00eb versionet e fundit t\u00eb Firefox, lejohet deri n\u00eb gjasht\u00eb lidhje.<br \/>\n<img decoding=\"async\" alt=\"HTTP\/3: shkat\u00ebrrimi i themelieve dhe bota e re e mrekullueshme\" src=\"\/wp-content\/uploads\/2019\/11\/b1c131da8e62ace741f3064f2fb96c60.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nEnkriptimi gjithashtu supozohej t\u00eb lihej n\u00eb dor\u00eb protokoll\u00ebve t\u00eb tjer\u00eb, dhe p\u00ebr k\u00ebt\u00eb, mbi TCP filloi t\u00eb p\u00ebrdorej protokolli TLS, i cili siguronte t\u00eb dh\u00ebnat mjaft besuesh\u00ebm, por gjithashtu rriti edhe m\u00eb shum\u00eb koh\u00ebn e nevojshme p\u00ebr krijimin e lidhjes. Si rezultat, procesi i dor\u00ebzim-it u duk k\u00ebshtu:<br \/>\n <img decoding=\"async\" alt=\"HTTP\/3: shkat\u00ebrrimi i themelieve dhe bota e re e mrekullueshme\" src=\"\/wp-content\/uploads\/2019\/11\/2fdccf56e0ed29444557836fdc65351b.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<i>Ilustrimi i Cloudflare<\/i><\/p>\n<p>K\u00ebshtu HTTP\/1.1 kishte disa probleme:<\/p>\n<ul>\n<li>Instalim i ngadalt\u00eb i lidhjes.<\/li>\n<li>T\u00eb dh\u00ebnat transmetohen n\u00eb form\u00eb tekstuale, q\u00eb do t\u00eb thot\u00eb se transmetimi i imazheve, videove dhe informacionit tjet\u00ebr jo tekstual \u00ebsht\u00eb joefikas.<\/li>\n<li>Nj\u00eb lidhje TCP p\u00ebrdoret p\u00ebr nj\u00eb k\u00ebrkes\u00eb, q\u00eb do t\u00eb thot\u00eb se k\u00ebrkesat e tjera ose duhet t\u00eb gjejn\u00eb nj\u00eb lidhje tjet\u00ebr ose t\u00eb presin derisa k\u00ebrkesa aktuale ta liroj\u00eb at\u00eb.<\/li>\n<li>Mb\u00ebshtetet vet\u00ebm modeli pull. N\u00eb standart nuk ka asgj\u00eb p\u00ebr server-push.<\/li>\n<li>Kryesit transmetohen si tekst.<\/li>\n<\/ul>\n<p>\nN\u00ebse server-push realizohet me ndihm\u00ebn e protokollit WebSocket, at\u00ebher\u00eb p\u00ebr problemet e tjera duhej t\u00eb merreshin masa m\u00eb radikale.<\/p>\n<h2>Pak modernizim: HTTP\/2<\/h2>\n<p>\nN\u00eb vitin 2012, n\u00eb rrjedhat e Google nisi puna p\u00ebr protokollin SPDY (t\u00eb cilin e shqiptojm\u00eb \"spidi\"). Protokolli ishte krijuar p\u00ebr t\u00eb zgjidhur problemet kryesore t\u00eb HTTP\/1.1 dhe n\u00eb t\u00eb nj\u00ebjt\u00ebn koh\u00eb duhej t\u00eb ruante p\u00ebrputhshm\u00ebrin\u00eb me versionin e m\u00ebparsh\u00ebm. N\u00eb vitin 2015, grupi punues i IETF paraqiti specifikimin HTTP\/2, t\u00eb bazuar n\u00eb protokollin SPDY. Ja \u00e7far\u00eb dallimesh kishte n\u00eb HTTP\/2:<\/p>\n<ul>\n<li>Serializimi binar.<\/li>\n<li>Multipleximi i k\u00ebrkesave t\u00eb shumta HTTP n\u00eb nj\u00eb lidhje TCP.<\/li>\n<li>Server-push nga kutia (pa WebSocket).<\/li>\n<\/ul>\n<p>\nProtokolli b\u00ebri nj\u00eb hap t\u00eb madh p\u00ebrpara. Ai ndjesh\u00ebm <noindex><a rel=\"nofollow\" href=\"https:\/\/http2.akamai.com\/demo\">fiton mbi versionin e par\u00eb n\u00eb shpejt\u00ebsi<\/a><\/noindex> dhe nuk k\u00ebrkon krijimin e disa lidhjeve TCP: t\u00eb gjitha k\u00ebrkesat ndaj nj\u00eb host-i jan\u00eb t\u00eb mnohuara n\u00eb nj\u00eb. Pra, n\u00eb nj\u00eb lidhje jan\u00eb disa rrjedha t\u00eb quajtura, secila prej t\u00eb cilave ka ID-n\u00eb e saj. Nj\u00eb bonus \u00ebsht\u00eb server-push i paketuar.<\/p>\n<p>Megjithat\u00eb, multipleximi sjell nj\u00eb tjet\u00ebr problem themelor. Imagjinoni se ne ekzekutojm\u00eb asinkronisht 5 k\u00ebrkesa ndaj nj\u00eb serveri. P\u00ebrdorimi i HTTP\/2 do t\u00eb thot\u00eb se t\u00eb gjitha k\u00ebto k\u00ebrkesa do t\u00eb ekzekutohen brenda nj\u00eb lidhjeje TCP, q\u00eb do t\u00eb thot\u00eb se n\u00ebse nj\u00eb nga segmentet e \u00e7do k\u00ebrkese humbet ose vjen gabim, transmetimi i t\u00eb gjitha k\u00ebrkesave dhe p\u00ebrgjigjeve do t\u00eb ndalet derisa t\u00eb rikuperohet segmenti i humbur. Ose, sa m\u00eb keq t\u00eb jet\u00eb cil\u00ebsia e lidhjes, aq m\u00eb ngadal\u00eb funksionon HTTP\/2. <noindex><a rel=\"nofollow\" href=\"https:\/\/http3-explained.haxx.se\/en\/why-tcphol.html\">Sipas vler\u00ebsimit t\u00eb Daniel Steinberg<\/a><\/noindex>, n\u00eb kushte ku paketat e humbura p\u00ebrb\u00ebjn\u00eb 2% t\u00eb gjith\u00ebve, HTTP\/1.1 n\u00eb shfletues tregon performanc\u00eb m\u00eb t\u00eb mir\u00eb se HTTP\/2, p\u00ebr shkak se hap 6 lidhje, dhe jo nj\u00eb.<\/p>\n<p>Ky problem quhet \"head-of-line blocking\" dhe, fatkeq\u00ebsisht, zgjidhja e tij duke p\u00ebrdorur TCP nuk duket e mundshme.<br \/>\n<img decoding=\"async\" alt=\"HTTP\/3: shkat\u00ebrrimi i themelieve dhe bota e re e mrekullueshme\" src=\"\/wp-content\/uploads\/2019\/11\/234a6dc218a9acf8d2212fbdf28f2188.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<i>Ilustrimi Daniel Steinberg<\/i><\/p>\n<p>Si p\u00ebrfundim, zhvilluesit e standardit HTTP\/2 b\u00ebn\u00eb nj\u00eb pun\u00eb t\u00eb madhe dhe bllokuan pothuajse gjith\u00e7ka q\u00eb mund t\u00eb shkonte b\u00ebr\u00eb n\u00eb nivelin aplikativ t\u00eb modelit OSI. \u00cbsht\u00eb koha t\u00eb zbresim n\u00eb nivelin e transportit dhe t\u00eb shpikim nj\u00eb protokoll t\u00eb ri transporti.<\/p>\n<h2>Na nevojitet nj\u00eb protokoll i ri: UDP vs TCP<\/h2>\n<p>\n\u0414\u043e\u0432\u043e\u043b\u044c\u043d\u043e \u0431\u044b\u0441\u0442\u0440\u043e \u0441\u0442\u0430\u043b\u043e \u043f\u043e\u043d\u044f\u0442\u043d\u043e, \u0447\u0442\u043e \u0432\u043d\u0435\u0434\u0440\u0438\u0442\u044c \u0441\u043e\u0432\u0441\u0435\u043c \u043d\u043e\u0432\u044b\u0439 \u043f\u0440\u043e\u0442\u043e\u043a\u043e\u043b \u0442\u0440\u0430\u043d\u0441\u043f\u043e\u0440\u0442\u043d\u043e\u0433\u043e \u0443\u0440\u043e\u0432\u043d\u044f \u2013 \u0437\u0430\u0434\u0430\u0447\u0430 \u0432 \u0441\u0435\u0433\u043e\u0434\u043d\u044f\u0448\u043d\u0438\u0445 \u0440\u0435\u0430\u043b\u0438\u044f\u0445 \u043d\u0435\u0440\u0435\u0448\u0430\u0435\u043c\u0430\u044f. \u0414\u0435\u043b\u043e \u0432 \u0442\u043e\u043c, \u0447\u0442\u043e \u043e \u0442\u0440\u0430\u043d\u0441\u043f\u043e\u0440\u0442\u043d\u043e\u043c \u0443\u0440\u043e\u0432\u043d\u0435 \u0437\u043d\u0430\u044e\u0442 \u0436\u0435\u043b\u0435\u0437\u043a\u0438 \u0438\u043b\u0438 middle-boxes (\u0440\u043e\u0443\u0442\u0435\u0440\u044b, \u0444\u0430\u0439\u0440\u0432\u043e\u043b\u044b, NAT-\u0441\u0435\u0440\u0432\u0435\u0440\u044b&#8230;), \u0430 \u043d\u0430\u0443\u0447\u0438\u0442\u044c \u0438\u0445 \u0447\u0435\u043c\u0443-\u0442\u043e \u043d\u043e\u0432\u043e\u043c\u0443 \u043a\u0440\u0430\u0439\u043d\u0435 \u043d\u0435\u043f\u0440\u043e\u0441\u0442\u0430\u044f \u0437\u0430\u0434\u0430\u0447\u0430. \u041a\u0440\u043e\u043c\u0435 \u0442\u043e\u0433\u043e, \u043f\u043e\u0434\u0434\u0435\u0440\u0436\u043a\u0430 \u0442\u0440\u0430\u043d\u0441\u043f\u043e\u0440\u0442\u043d\u044b\u0445 \u043f\u0440\u043e\u0442\u043e\u043a\u043e\u043b\u043e\u0432 \u0437\u0430\u0448\u0438\u0442\u0430 \u0432 \u044f\u0434\u0440\u043e \u043e\u043f\u0435\u0440\u0430\u0446\u0438\u043e\u043d\u043d\u044b\u0445 \u0441\u0438\u0441\u0442\u0435\u043c, \u0430 \u044f\u0434\u0440\u0430 \u0442\u043e\u0436\u0435 \u043c\u0435\u043d\u044f\u044e\u0442\u0441\u044f \u043d\u0435 \u0442\u043e \u0447\u0442\u043e\u0431\u044b \u043e\u0447\u0435\u043d\u044c \u043e\u0445\u043e\u0442\u043d\u043e.<\/p>\n<p>Dhe k\u00ebtu do t\u00eb mund t\u00eb dor\u00ebzohej dhe t\u00eb thuhej \"Ne, sigurisht, do t\u00eb shpikim HTTP\/3 me preferenc\u00eb dhe kurtezana, por ai do t\u00eb implementohet pas 10-15 vitesh (p\u00ebr rreth nj\u00eb koh\u00eb t\u00eb till\u00eb shumica e pajisjeve do t\u00eb z\u00ebvend\u00ebsohen)\", por ka nj\u00eb mund\u00ebsi tjet\u00ebr, jo aq t\u00eb dukshme: t\u00eb p\u00ebrdorim protokollin UDP. Po, po, ai protokoll, me t\u00eb cilin ne d\u00ebrgonim skedar\u00eb n\u00eb LAN n\u00eb fund t\u00eb viteve '90 dhe fillim t\u00eb viteve 2000. Pothuajse t\u00eb gjitha pajisjet e sotme din\u00eb ta p\u00ebrdorin at\u00eb.<\/p>\n<p>Cilat jan\u00eb avantazhet e UDP krahasuar me TCP? N\u00eb radh\u00eb t\u00eb par\u00eb, se ne nuk kemi nj\u00eb sesion t\u00eb nivelit t\u00eb transportit, p\u00ebr t\u00eb cilin pajisjet e din\u00eb. Kjo na lejon t\u00eb p\u00ebrcaktojm\u00eb vet\u00eb sesionin n\u00eb pik\u00ebt e fundit dhe t\u00eb zgjidhim konfliktet q\u00eb lindin aty. Pra, ne nuk jemi t\u00eb kufizuar n\u00eb nj\u00eb ose disa seanca (si\u00e7 \u00ebsht\u00eb n\u00eb TCP), por mund t\u00eb krijojm\u00eb sa m\u00eb shum\u00eb seanca sa na nevojitet. N\u00eb t\u00eb dyt\u00ebn, transferimi i t\u00eb dh\u00ebnave p\u00ebrmes UDP ndodh m\u00eb shpejt se n\u00eb TCP. K\u00ebshtu, n\u00eb teori, ne mund t\u00eb kalojm\u00eb kufirin e shpejt\u00ebsis\u00eb sot, t\u00eb arritur n\u00eb HTTP\/2. <\/p>\n<p>Megjithat\u00eb, UDP nuk garanton besueshm\u00ebrin\u00eb e transferimit t\u00eb t\u00eb dh\u00ebnave. N\u00eb fakt, ne thjesht d\u00ebrgojm\u00eb paketa, duke shpresuar q\u00eb ato do t\u00eb priten n\u00eb an\u00ebn tjet\u00ebr. Nuk u priten? Epo, nuk pat\u00ebm fat... Kjo ishte e mjaftueshme p\u00ebr transmetimin e videove p\u00ebr t\u00eb rritur, por p\u00ebr gj\u00ebra m\u00eb serioze nevojitet besueshm\u00ebri, dhe k\u00ebshtu q\u00eb do t\u00eb duhet t\u00eb shtojm\u00eb di\u00e7ka tjet\u00ebr mbi UDP.<\/p>\n<p>Si dhe n\u00eb rastin e HTTP\/2, puna p\u00ebr krijimin e nj\u00eb protokolli t\u00eb ri filloi n\u00eb Google n\u00eb vitin 2012, pra rreth t\u00eb nj\u00ebjt\u00ebs koh\u00eb me fillimin e pun\u00ebs mbi SPDY. N\u00eb vitin 2013, Jim Roskind e paraqiti at\u00eb p\u00ebr publikun. <noindex><a rel=\"nofollow\" href=\"https:\/\/docs.google.com\/document\/d\/1RNHkx_VvKWyWg6Lr8SZ-saqsQx7rFV-ev2jRFUoVD34\/edit\">protokollin QUIC (Quick UDP Internet Connections)<\/a><\/noindex>, dhe n\u00eb vitin 2015 u paraqit nj\u00eb Draft Interneti p\u00ebr standardizimin n\u00eb IETF. N\u00eb at\u00eb koh\u00eb, protokolli i zhvilluar nga Roskind n\u00eb Google ishte shum\u00eb ndryshe nga ai i propozuar p\u00ebr standard, k\u00ebshtu q\u00eb versioni i Google u quajt gQUIC.<\/p>\n<h4>\u00c7far\u00eb \u00ebsht\u00eb QUIC<\/h4>\n<p>\nS\u00eb pari, si\u00e7 u tha tashm\u00eb, \u00ebsht\u00eb nj\u00eb mb\u00ebshtetje mbi UDP. P\u00ebrsip\u00ebr UDP krijohet nj\u00eb lidhje QUIC, n\u00eb t\u00eb cil\u00ebn, sipas analogjis\u00eb me HTTP\/2, mund t\u00eb ekzistojn\u00eb disa rrjedha. K\u00ebto rrjedha ekzistojn\u00eb vet\u00ebm n\u00eb pik\u00ebt p\u00ebrfundimtare dhe sh\u00ebrbehen n\u00eb m\u00ebnyr\u00eb t\u00eb pavarur. N\u00ebse ndodh humbja e nj\u00eb pakete n\u00eb nj\u00eb rrjedh\u00eb, t\u00eb tjerat nuk preken aspak.<br \/>\n<img decoding=\"async\" alt=\"HTTP\/3: shkat\u00ebrrimi i themelieve dhe bota e re e mrekullueshme\" src=\"\/wp-content\/uploads\/2019\/11\/0a64aa26d9b8216db56d389fa48578a5.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<i>Ilustrimi Daniel Steinberg<\/i><\/p>\n<p>S\u00eb dyti, enkriptimi tani implementohet jo si nj\u00eb nivel i ve\u00e7ant\u00eb, por \u00ebsht\u00eb i p\u00ebrfshir\u00eb n\u00eb protokoll. Kjo mund\u00ebson vendosjen e lidhjes dhe shk\u00ebmbimin e \u00e7el save publike n\u00eb nj\u00eb dor\u00ebheqje, si dhe p\u00ebrdorimin e mekanizmit t\u00eb ve\u00e7ant\u00eb 0-RTT handshake, duke shmangur vonesat gjat\u00eb dor\u00ebheqjes. P\u00ebr m\u00eb tep\u00ebr, tani \u00ebsht\u00eb e mundur t\u00eb enkriptohen paketa t\u00eb ve\u00e7anta t\u00eb dh\u00ebnash. Kjo lejon q\u00eb t\u00eb mos pritet p\u00ebrfundimi i marrjes s\u00eb t\u00eb dh\u00ebnave nga rrjedha, por t\u00eb dekriptohen paketat e marra n\u00eb m\u00ebnyr\u00eb t\u00eb pavarur. Ky m\u00ebnyr\u00eb funksionimi ishte krejt\u00ebsisht e pamundur n\u00eb TCP, pasi TLS dhe TCP punonin n\u00eb m\u00ebnyr\u00eb t\u00eb pavarur nga nj\u00ebri-tjetri, dhe TLS nuk mund t\u00eb dinte se n\u00eb cilat copa do t\u00eb cop\u00ebzoheshin t\u00eb dh\u00ebnat nga TCP. Prandaj, nuk mund t\u00eb p\u00ebrgatitej segmentet e tij n\u00eb m\u00ebnyr\u00eb q\u00eb ato t\u00eb p\u00ebrputheshin segmentet TCP nj\u00eb p\u00ebr nj\u00eb dhe t\u00eb ishin p\u00ebr t'u dekriptuar n\u00eb m\u00ebnyr\u00eb t\u00eb pavarur. T\u00eb gjitha k\u00ebto p\u00ebrmir\u00ebsime lejojn\u00eb QUIC t\u00eb ul\u00eb vones\u00ebn krahasuar me TCP.<br \/>\n<img decoding=\"async\" alt=\"HTTP\/3: shkat\u00ebrrimi i themelieve dhe bota e re e mrekullueshme\" src=\"\/wp-content\/uploads\/2019\/11\/cb3c522636f7a052a0f5988fe7ea3a65.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nS\u00eb treti, koncepti i rrjedhave t\u00eb lehta lejon ndarjen e lidhjes nga adresa IP e klientit. Kjo \u00ebsht\u00eb e r\u00ebnd\u00ebsishme, p\u00ebr shembull, kur klienti kalon nga nj\u00eb pik\u00eb qasjeje Wi-Fi n\u00eb nj\u00eb tjet\u00ebr, duke ndryshuar IP-n\u00eb e tij. N\u00eb k\u00ebt\u00eb rast, duke p\u00ebrdorur TCP ndodh nj\u00eb proces i gjat\u00eb, gjat\u00eb t\u00eb cilit lidhjet ekzistuese TCP bien p\u00ebr shkak t\u00eb koh\u00ebs s\u00eb pritjes dhe krijohen lidhje t\u00eb reja me IP-n\u00eb e re. N\u00eb rastin e QUIC, klienti vazhdon thjesht t\u00eb d\u00ebrgoj\u00eb paketa serverit me IP-n\u00eb e re dhe ID-n\u00eb e vjet\u00ebr t\u00eb rrjedh\u00ebs. Duke qen\u00eb se ID-ja e rrjedh\u00ebs tani \u00ebsht\u00eb unike dhe nuk ri-p\u00ebrdoret, serveri kupton se klienti ka ndryshuar IP-n\u00eb, d\u00ebrgon paketat e humbura dhe vazhdon komunikimin me adres\u00ebn e re.<\/p>\n<p>S\u00eb fundmi, QUIC implementohet n\u00eb nivelin e aplikacionit dhe jo n\u00eb nivelin e sistemit operative. Kjo, nga nj\u00ebra an\u00eb, lejon t\u00eb b\u00ebhen ndryshime m\u00eb shpejta n\u00eb protokoll, sepse p\u00ebr t\u00eb marr\u00eb nj\u00eb p\u00ebrdit\u00ebsim mjafton t\u00eb azhurnosh bibliotek\u00ebn, dhe jo t\u00eb pres\u00ebsh nj\u00eb version t\u00eb ri t\u00eb OS-s\u00eb. Nga ana tjet\u00ebr, kjo \u00e7on n\u00eb nj\u00eb rritje t\u00eb konsiderueshme t\u00eb p\u00ebrdorimit t\u00eb procesorit.<\/p>\n<p>Dhe si p\u00ebrfundim, titujt. Kompresimi i titujve \u00ebsht\u00eb pik\u00ebrisht nj\u00eb nga ato elemente q\u00eb ndryshojn\u00eb n\u00eb QUIC dhe gQUIC. Nuk e shoh t\u00eb arsyeshme t\u00eb kushtoj shum\u00eb koh\u00eb k\u00ebsaj, do t\u00eb thosha vet\u00ebm se n\u00eb versionin e paraqitur p\u00ebr standardizim, kompresimi i titujve u b\u00eb maksimalisht i ngjash\u00ebm me kompresimin e titujve n\u00eb HTTP\/2. M\u00eb shum\u00eb mund t\u00eb lexoni <noindex><a rel=\"nofollow\" href=\"https:\/\/blog.cloudflare.com\/the-road-to-quic\/\">k\u00ebtu<\/a><\/noindex>.<\/p>\n<h4>Sa m\u00eb shpejt \u00ebsht\u00eb?<\/h4>\n<p>\nKy \u00ebsht\u00eb nj\u00eb pyetje e komplikuar. Problemi \u00ebsht\u00eb se deri tani nuk kemi nj\u00eb standard, prandaj nuk ka shum\u00eb p\u00ebr t\u00eb matur. Ndoshta, t\u00eb dh\u00ebnat statistikore t\u00eb vetme q\u00eb kemi \u2013 statistikat e Google q\u00eb nga viti 2013 e deri m\u00eb 2016 <noindex><a rel=\"nofollow\" href=\"https:\/\/www.ietf.org\/proceedings\/96\/slides\/slides-96-quic-3.pdf\">raportuan p\u00ebr IETF<\/a><\/noindex>, se rreth 90% e trafikut q\u00eb shkon n\u00eb serverat e tyre nga shfletuesi Chrome tani p\u00ebrdor QUIC. N\u00eb t\u00eb nj\u00ebjt\u00ebn prezantim ata njoftojn\u00eb se p\u00ebrmes gQUIC, faqet e internetit ngarkohen rreth 5% m\u00eb shpejt, nd\u00ebrsa n\u00eb video streaming ka 30% m\u00eb pak ngecje krahasuar me TCP. <\/p>\n<p>N\u00eb vitin 2017, nj\u00eb grup hulumtuesish n\u00ebn drejtimin e Arash Molavi Kakhki publikoi <noindex><a rel=\"nofollow\" href=\"https:\/\/conferences.sigcomm.org\/imc\/2017\/papers\/imc17-final39.pdf\">nj\u00eb punim t\u00eb madh<\/a><\/noindex> p\u00ebr studimin e performanc\u00ebs s\u00eb gQUIC krahasuar me TCP. <br \/>\nStudimi zbuloi disa dob\u00ebsi t\u00eb gQUIC, si\u00e7 jan\u00eb pasiguria ndaj p\u00ebrzierjes s\u00eb paketave t\u00eb rrjetit, lakmia (n\u00eb m\u00ebnyr\u00eb t\u00eb padrejt\u00eb) ndaj bant\u00ebs s\u00eb kanalit dhe transmetimi m\u00eb i ngadalt\u00eb i objekteve t\u00eb vogla (deri n\u00eb 10 kB). Sidoqoft\u00eb, kjo e fundit mund t\u00eb kompensohet duke p\u00ebrdorur 0-RTT. N\u00eb t\u00eb gjitha rastet e tjera t\u00eb hulumtuara, gQUIC tregoi nj\u00eb rritje t\u00eb shpejt\u00ebsis\u00eb krahasuar me TCP. P\u00ebr numra konkret\u00eb k\u00ebtu \u00ebsht\u00eb e v\u00ebshtir\u00eb t\u00eb flasim. M\u00eb mir\u00eb t\u00eb lexoni <noindex><a rel=\"nofollow\" href=\"https:\/\/conferences.sigcomm.org\/imc\/2017\/papers\/imc17-final39.pdf\">studimin e vet\u00eb<\/a><\/noindex> \u0438\u043b\u0438 <noindex><a rel=\"nofollow\" href=\"https:\/\/blog.apnic.net\/2018\/01\/29\/measuring-quic-vs-tcp-mobile-desktop\/\">nj\u00eb post t\u00eb shkurt\u00ebr<\/a><\/noindex>.<\/p>\n<p>K\u00ebtu duhet th\u00ebn\u00eb se k\u00ebto jan\u00eb t\u00eb dh\u00ebna pik\u00ebrisht p\u00ebr gQUIC, dhe ato nuk jan\u00eb aktuale p\u00ebr standardin n\u00eb zhvillim. \u00c7far\u00eb do t\u00eb ndodh\u00eb me QUIC: p\u00ebr momentin mbetet nj\u00eb mister, por ka shpres\u00eb q\u00eb dob\u00ebsit\u00eb e zbuluara te gQUIC do t\u00eb merreshin parasysh dhe do t\u00eb rregulloheshin.<\/p>\n<h2>Pak p\u00ebr t\u00eb ardhmen: \u00e7far\u00eb do t\u00eb ndodh\u00eb me HTTP\/3?<\/h2>\n<p>\nDhe, k\u00ebtu \u00ebsht\u00eb gjith\u00e7ka e qart\u00eb: API nuk do t\u00eb ndryshoj\u00eb. T\u00eb gjitha do t\u00eb mbeten ashtu si\u00e7 ishin n\u00eb HTTP\/2. N\u00ebse API mbetet e nj\u00ebjt\u00eb, kalimi n\u00eb HTTP\/3 do t\u00eb duhet t\u00eb realizohet duke p\u00ebrdorur nj\u00eb version t\u00eb ri t\u00eb bibliotek\u00ebs n\u00eb backend q\u00eb mb\u00ebshtet transportin p\u00ebrmes QUIC. Megjithat\u00eb, do t\u00eb jet\u00eb shum\u00eb koh\u00eb deri sa t\u00eb kemi nj\u00eb kalim t\u00eb plot\u00eb n\u00eb UDP, sepse interneti aktualisht nuk \u00ebsht\u00eb i gatsh\u00ebm p\u00ebr k\u00ebt\u00eb.<\/p>\n<h4>Kush mb\u00ebshtet tashm\u00eb<\/h4>\n<p>\nJa <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/quicwg\/base-drafts\/wiki\/Implementations\">lista<\/a><\/noindex> implementime ekzistuese t\u00eb QUIC. Megjith\u00ebse nuk ka nj\u00eb standard, lista \u00ebsht\u00eb e mir\u00eb. <\/p>\n<p>Asnj\u00eb shfletues aktualisht nuk mb\u00ebshtet QUIC n\u00eb versionin prodhues. Koh\u00ebt e fundit kishte informacione se Chrome kishte aktivizuar mb\u00ebshtetje p\u00ebr HTTP\/3, por p\u00ebr momentin vet\u00ebm n\u00eb Canary. <\/p>\n<p>Nga backend-et, HTTP\/3 mb\u00ebshtetet vet\u00ebm <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/caddyserver\/caddy\">Caddy<\/a><\/noindex> \u0438 <noindex><a rel=\"nofollow\" href=\"https:\/\/blog.cloudflare.com\/http3-the-past-present-and-future\/\">Cloudflare<\/a><\/noindex>, por p\u00ebr momentin eksperimental. NGINX n\u00eb fund t\u00eb pranver\u00ebs 2019 <noindex><a rel=\"nofollow\" href=\"https:\/\/www.nginx.com\/blog\/nginx-1-16-1-17-released\/\">njoftuan<\/a><\/noindex>, q\u00eb filluan pun\u00ebn p\u00ebr t\u00eb mb\u00ebshtetur HTTP\/3, por ende nuk e kan\u00eb p\u00ebrfunduar.<\/p>\n<h4>Cilat jan\u00eb problemet<\/h4>\n<p>\nNe jetojm\u00eb n\u00eb nj\u00eb bot\u00eb reale, ku asnj\u00eb teknologji e madhe nuk mund t\u00eb kaloj\u00eb n\u00eb masat pa u p\u00ebrballur me rezistenc\u00eb, dhe QUIC nuk \u00ebsht\u00eb p\u00ebrjashtim.<\/p>\n<p>M\u00eb e r\u00ebnd\u00ebsishmja, duhet ndonj\u00ebher\u00eb t\u00eb shpjegohet shfletuesit se \u201chttps:\/\/\u201d tani nuk \u00ebsht\u00eb e sigurt q\u00eb \u00e7on n\u00eb portin TCP 443. Atje mund t\u00eb mos ket\u00eb fare TCP. P\u00ebr k\u00ebt\u00eb p\u00ebrdoret titulli Alt-Svc. Ai lejon t\u00eb njoftosh shfletuesin se ky uebsajt \u00ebsht\u00eb gjithashtu i aksesuesh\u00ebm n\u00eb nj\u00eb protokoll t\u00eb till\u00eb n\u00eb nj\u00eb adres\u00eb t\u00eb till\u00eb. N\u00eb teori, kjo duhet t\u00eb funksionoj\u00eb si or\u00eb, por praktikisht do t\u00eb hasim n\u00eb at\u00eb q\u00eb UDP mund t\u00eb jet\u00eb, p\u00ebr shembull, i ndaluar n\u00eb firewall p\u00ebr t\u00eb shmangur sulmet DDoS.<\/p>\n<p>Por edhe n\u00ebse UDP nuk \u00ebsht\u00eb i ndaluar, klienti mund t\u00eb jet\u00eb n\u00ebn nj\u00eb router NAT i cili \u00ebsht\u00eb konfiguruar p\u00ebr t\u00eb mbajtur sesionin TCP mbi adres\u00ebn IP, dhe pasi ne p\u00ebrdorim UDP, n\u00eb t\u00eb cilin nuk ka nj\u00eb sesion t\u00eb pajisjeve, NAT nuk do t\u00eb mbaj\u00eb lidhjen, dhe seanca QUIC <noindex><a rel=\"nofollow\" href=\"https:\/\/blog.cloudflare.com\/the-road-to-quic\/\">do t\u00eb shqet\u00ebsuar vazhdimisht<\/a><\/noindex>. <\/p>\n<p>T\u00eb gjitha k\u00ebto probleme lidhen me faktin se UDP nuk \u00ebsht\u00eb p\u00ebrdorur m\u00eb par\u00eb p\u00ebr transmetimin e p\u00ebrmbajtjes n\u00eb internet, dhe prodhuesit e pajisjeve nuk mund t\u00eb parashikonin se kjo do t\u00eb ndodhte nj\u00eb dit\u00eb. Po ashtu, administrator\u00ebt nuk e kuptojn\u00eb ende mir\u00eb se si t\u00eb konfirmojn\u00eb rrjetet e tyre p\u00ebr t\u00eb punuar me QUIC. Ky situat\u00eb do t\u00eb ndryshoj\u00eb gradualisht, dhe n\u00eb \u00e7do rast, k\u00ebto ndryshime do t\u00eb marrin m\u00eb pak koh\u00eb se sa implementimi i nj\u00eb protokolli t\u00eb ri t\u00eb nivelit t\u00eb transportit. <\/p>\n<p>P\u00ebrve\u00e7 k\u00ebsaj, si\u00e7 \u00ebsht\u00eb p\u00ebrshkruar m\u00eb par\u00eb, QUIC ndjesh\u00ebm rrit p\u00ebrdorimin e procesorit. Daniel Stenberg <noindex><a rel=\"nofollow\" href=\"https:\/\/www.youtube.com\/watch?v=idViw4anA6E\">vler\u00ebsoi<\/a><\/noindex> rritjen n\u00eb procesor deri n\u00eb tre her\u00eb.<\/p>\n<h4>Kur do t\u00eb vij\u00eb HTTP\/3<\/h4>\n<p>\nStandarti <noindex><a rel=\"nofollow\" href=\"https:\/\/datatracker.ietf.org\/wg\/quic\/about\/\">do t\u00eb miratohet<\/a><\/noindex> N\u00eb maj t\u00eb vitit 2020, por duke marr\u00eb parasysh q\u00eb deri tani dokumentet e planifikuara p\u00ebr korrik 2019 jan\u00eb ende t\u00eb pap\u00ebrfunduara, mund t\u00eb thuhet se data p\u00ebr k\u00ebt\u00eb ka shum\u00eb t\u00eb ngjar\u00eb t\u00eb shtyhet.<\/p>\n<p>Nd\u00ebrsa Google p\u00ebrdor realizimin e tij t\u00eb gQUIC q\u00eb nga viti 2013. N\u00ebse shikoni k\u00ebrkes\u00ebn HTTP q\u00eb d\u00ebrgohet n\u00eb motorin e k\u00ebrkimit t\u00eb Google, mund t\u00eb shihni k\u00ebt\u00eb:<br \/>\n<img decoding=\"async\" alt=\"HTTP\/3: shkat\u00ebrrimi i themelieve dhe bota e re e mrekullueshme\" src=\"\/wp-content\/uploads\/2019\/11\/af422268eb85b488c7be1b70c6d33fad.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<h2>P\u00ebrfundimet<\/h2>\n<p>\nQUIC tani duket si nj\u00eb teknologji mjaft e papjekur, por me shum\u00eb potencial. Duke pasur parasysh se gjat\u00eb 20 viteve t\u00eb fundit t\u00eb gjitha optimizimet e protokolleve t\u00eb nivelit t\u00eb transportit kan\u00eb pasur si fokus kryesor TCP, QUIC, q\u00eb n\u00eb shumic\u00ebn e rasteve fiton n\u00eb performanc\u00eb, duket tashm\u00eb shum\u00eb mir\u00eb. <\/p>\n<p>Megjithat\u00eb, ende ka disa probleme t\u00eb pa zgjidhura q\u00eb do t\u00eb duhet t\u00eb trajtohen n\u00eb vitet e ardhshme. Procesi mund t\u00eb zgjatet p\u00ebr shkak t\u00eb harduerit q\u00eb askush nuk e do t\u00eb azhurnoj\u00eb, megjithat\u00eb, t\u00eb gjitha problemet duken mjaft t\u00eb zgjidhshme dhe von\u00eb a her\u00ebt t\u00eb gjith\u00ebve do t\u00eb kemi HTTP\/3. <\/p>\n<p>T\u00eb ardhmen nuk \u00ebsht\u00eb larg!<br \/>\n<br \/>Burimi: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/dodopizzaio\/blog\/473930\/\">habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u0412\u043e\u0442 \u0443\u0436\u0435 \u0431\u043e\u043b\u044c\u0448\u0435 20 \u043b\u0435\u0442 \u043c\u044b \u0441\u043c\u043e\u0442\u0440\u0438\u043c \u0432\u0435\u0431-\u0441\u0442\u0440\u0430\u043d\u0438\u0447\u043a\u0438 \u043f\u043e \u043f\u0440\u043e\u0442\u043e\u043a\u043e\u043b\u0443 HTTP. \u0411\u043e\u043b\u044c\u0448\u0438\u043d\u0441\u0442\u0432\u043e \u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u0435\u043b\u0435\u0439 \u0432\u043e\u043e\u0431\u0449\u0435 \u043d\u0435 \u0437\u0430\u0434\u0443\u043c\u044b\u0432\u0430\u0435\u0442\u0441\u044f \u043e \u0442\u043e\u043c, \u0447\u0442\u043e \u044d\u0442\u043e \u0442\u0430\u043a\u043e\u0435 \u0438 \u043a\u0430\u043a \u043e\u043d\u043e \u0440\u0430\u0431\u043e\u0442\u0430\u0435\u0442. \u0414\u0440\u0443\u0433\u0438\u0435 \u0437\u043d\u0430\u044e\u0442, \u0447\u0442\u043e \u0433\u0434\u0435-\u0442\u043e \u043f\u043e\u0434 HTTP \u0435\u0441\u0442\u044c TLS, \u0430 \u043f\u043e\u0434 \u043d\u0438\u043c TCP, \u043f\u043e\u0434 \u043a\u043e\u0442\u043e\u0440\u044b\u043c IP \u0438 \u0442\u0430\u043a \u0434\u0430\u043b\u0435\u0435. \u0410 \u0442\u0440\u0435\u0442\u044c\u0438 \u2013 \u0435\u0440\u0435\u0442\u0438\u043a\u0438 \u2013 \u0441\u0447\u0438\u0442\u0430\u044e\u0442, \u0447\u0442\u043e TCP \u2013 \u044d\u0442\u043e \u043f\u0440\u043e\u0448\u043b\u044b\u0439 \u0432\u0435\u043a, [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-52181","post","type-post","status-publish","format-standard","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 5.0.1.1 - aioseo.com -->\n\t<meta name=\"description\" content=\"\u0412\u043e\u0442 \u0443\u0436\u0435 \u0431\u043e\u043b\u044c\u0448\u0435 20 \u043b\u0435\u0442 \u043c\u044b \u0441\u043c\u043e\u0442\u0440\u0438\u043c \u0432\u0435\u0431-\u0441\u0442\u0440\u0430\u043d\u0438\u0447\u043a\u0438 \u043f\u043e \u043f\u0440\u043e\u0442\u043e\u043a\u043e\u043b\u0443 HTTP. \u0411\u043e\u043b\u044c\u0448\u0438\u043d\u0441\u0442\u0432\u043e \u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u0435\u043b\u0435\u0439 \u0432\u043e\u043e\u0431\u0449\u0435 \u043d\u0435 \u0437\u0430\u0434\u0443\u043c\u044b\u0432\u0430\u0435\u0442\u0441\u044f \u043e \u0442\u043e\u043c, \u0447\u0442\u043e \u044d\u0442\u043e \u0442\u0430\u043a\u043e\u0435 \u0438 \u043a\u0430\u043a \u043e\u043d\u043e \u0440\u0430\u0431\u043e\u0442\u0430\u0435\u0442.\" \/>\n\t<meta name=\"robots\" content=\"max-image-preview:large\" \/>\n\t<meta name=\"author\" content=\"Yuri Gagarin\"\/>\n\t<link rel=\"canonical\" href=\"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/http-3-razrushenie-osnov-i-divnyj-novyj-mir\" \/>\n\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.1.1\" \/>\n\t\t<meta property=\"og:locale\" content=\"sq_AL\" \/>\n\t\t<meta property=\"og:site_name\" content=\"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b\" \/>\n\t\t<meta property=\"og:type\" content=\"article\" \/>\n\t\t<meta property=\"og:title\" content=\"\ud83e\udd47HTTP\/3: \u0440\u0430\u0437\u0440\u0443\u0448\u0435\u043d\u0438\u0435 \u043e\u0441\u043d\u043e\u0432 \u0438 \u0434\u0438\u0432\u043d\u044b\u0439 \u043d\u043e\u0432\u044b\u0439 \u043c\u0438\u0440 | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u0412\u043e\u0442 \u0443\u0436\u0435 \u0431\u043e\u043b\u044c\u0448\u0435 20 \u043b\u0435\u0442 \u043c\u044b \u0441\u043c\u043e\u0442\u0440\u0438\u043c \u0432\u0435\u0431-\u0441\u0442\u0440\u0430\u043d\u0438\u0447\u043a\u0438 \u043f\u043e \u043f\u0440\u043e\u0442\u043e\u043a\u043e\u043b\u0443 HTTP. \u0411\u043e\u043b\u044c\u0448\u0438\u043d\u0441\u0442\u0432\u043e \u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u0435\u043b\u0435\u0439 \u0432\u043e\u043e\u0431\u0449\u0435 \u043d\u0435 \u0437\u0430\u0434\u0443\u043c\u044b\u0432\u0430\u0435\u0442\u0441\u044f \u043e \u0442\u043e\u043c, \u0447\u0442\u043e \u044d\u0442\u043e \u0442\u0430\u043a\u043e\u0435 \u0438 \u043a\u0430\u043a \u043e\u043d\u043e \u0440\u0430\u0431\u043e\u0442\u0430\u0435\u0442.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/http-3-razrushenie-osnov-i-divnyj-novyj-mir\" \/>\n\t\t<meta property=\"og:image\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:secure_url\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:width\" content=\"350\" \/>\n\t\t<meta property=\"og:image:height\" content=\"350\" \/>\n\t\t<meta property=\"article:published_time\" content=\"2019-11-01T21:00:00+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2020-02-18T10:59:51+00:00\" \/>\n\t\t<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<meta property=\"article:author\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<!-- All in One SEO -->\n\n","aioseo_head_json":{"title":"\ud83e\udd47HTTP\/3: shkat\u00ebrrimi i themeleve dhe bota e re e mrekullueshme | ProHoster","description":"Tashm\u00eb m\u00eb shum\u00eb se 20 vjet ne shikojm\u00eb faqe webi p\u00ebrmes protokollit HTTP. Pajisjet m\u00eb t\u00eb shumta p\u00ebrdoruesve as q\u00eb e mendojn\u00eb se \u00e7far\u00eb \u00ebsht\u00eb dhe si funksionon.","canonical_url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/http-3-razrushenie-osnov-i-divnyj-novyj-mir","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"sq_AL","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47HTTP\/3: \u0440\u0430\u0437\u0440\u0443\u0448\u0435\u043d\u0438\u0435 \u043e\u0441\u043d\u043e\u0432 \u0438 \u0434\u0438\u0432\u043d\u044b\u0439 \u043d\u043e\u0432\u044b\u0439 \u043c\u0438\u0440 | ProHoster","og:description":"\u0412\u043e\u0442 \u0443\u0436\u0435 \u0431\u043e\u043b\u044c\u0448\u0435 20 \u043b\u0435\u0442 \u043c\u044b \u0441\u043c\u043e\u0442\u0440\u0438\u043c \u0432\u0435\u0431-\u0441\u0442\u0440\u0430\u043d\u0438\u0447\u043a\u0438 \u043f\u043e \u043f\u0440\u043e\u0442\u043e\u043a\u043e\u043b\u0443 HTTP. \u0411\u043e\u043b\u044c\u0448\u0438\u043d\u0441\u0442\u0432\u043e \u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u0435\u043b\u0435\u0439 \u0432\u043e\u043e\u0431\u0449\u0435 \u043d\u0435 \u0437\u0430\u0434\u0443\u043c\u044b\u0432\u0430\u0435\u0442\u0441\u044f \u043e \u0442\u043e\u043c, \u0447\u0442\u043e \u044d\u0442\u043e \u0442\u0430\u043a\u043e\u0435 \u0438 \u043a\u0430\u043a \u043e\u043d\u043e \u0440\u0430\u0431\u043e\u0442\u0430\u0435\u0442.","og:url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/http-3-razrushenie-osnov-i-divnyj-novyj-mir","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2019-11-01T21:00:00+00:00","article:modified_time":"2020-02-18T10:59:51+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"52181","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":"2026-01-24 02:46:19","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-02-28 20:48:31","updated":"2026-01-24 02:46:19","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/52181","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/comments?post=52181"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/52181\/revisions"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media?parent=52181"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/categories?post=52181"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/tags?post=52181"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}