{"id":81847,"date":"2020-05-17T01:42:34","date_gmt":"2020-05-16T23:42:34","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/http-po-udp-ispolzuem-s-polzoj-protokol-quic"},"modified":"2020-05-17T01:42:34","modified_gmt":"2020-05-16T23:42:34","slug":"http-po-udp-ispolzuem-s-polzoj-protokol-quic","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/http-po-udp-ispolzuem-s-polzoj-protokol-quic","title":{"rendered":"HTTP mbi UDP \u2014 p\u00ebrdorni n\u00eb m\u00ebnyr\u00eb efektive protokollin QUIC","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

\"HTTP
\n
\nQUIC (Quick UDP Internet Connections) \u2014 \u00ebsht\u00eb nj\u00eb protokoll mbi UDP q\u00eb mb\u00ebshtet t\u00eb gjitha funksionalitetet e TCP, TLS dhe HTTP\/2 dhe zgjidh shumic\u00ebn e problemeve t\u00eb tyre. Ai shpesh quhet protokoll i ri ose \"eksperimental\", por ka qen\u00eb p\u00ebr nj\u00eb koh\u00eb t\u00eb gjat\u00eb p\u00ebrtej faz\u00ebs eksperimentale: zhvillimi i tij ka vazhduar p\u00ebr m\u00eb shum\u00eb se 7 vjet. Gjat\u00eb k\u00ebsaj kohe, protokolli ende nuk ka arritur t\u00eb b\u00ebhet standard, por \u00ebsht\u00eb p\u00ebrhapur gjer\u00ebsisht. P\u00ebr shembull, QUIC p\u00ebrdoret p\u00ebr t\u00eb p\u00ebrshpejtuar trafikun dhe p\u00ebr t\u00eb reduktuar vonesat n\u00eb rrjetet mobile nga gjigant\u00ebt si Google dhe Facebook, nd\u00ebrsa IETF shpalli forkun e tij si baz\u00eb p\u00ebr standardin HTTP\/3 (duke marr\u00eb parasysh q\u00eb HTTP\/2 p\u00ebrdor vet\u00ebm 44.8%<\/a><\/noindex> e faqeve).<\/a><\/noindex><\/p>\n

Koncepsi<\/h2>\n

\nQUIC u zhvillua si nj\u00eb z\u00ebvend\u00ebsim p\u00ebr TCP-in e vjet\u00ebruar, i cili fillimisht ishte projektuar p\u00ebr rrjete kabllore me nj\u00eb p\u00ebrqindje t\u00eb ul\u00ebt humbjesh. TCP d\u00ebrgon paketat n\u00eb rend, k\u00ebshtu q\u00eb n\u00ebse nj\u00eb paket\u00eb humbet, e gjith\u00eb rreshti ndalon (head-of-line blocking<\/a><\/noindex>), \u00e7ka ndikon negativisht n\u00eb cil\u00ebsin\u00eb dhe stabilitetin e lidhjes. P\u00ebr t\u00eb shmangur humbje masive, rrjetet celulare p\u00ebrdorin bufere t\u00eb m\u00ebdha, gj\u00eb q\u00eb \u00e7on n\u00eb tepric\u00eb dhe reagim t\u00eb gabuar t\u00eb protokollit (bufferbloat<\/a><\/noindex>). P\u00ebr m\u00eb tep\u00ebr, TCP shpenzon shum\u00eb koh\u00eb p\u00ebr t\u00eb vendosur lidhjen: k\u00ebrkesat SYN\/ACK dhe TLS shkojn\u00eb ve\u00e7mas, duke k\u00ebrkuar tre roundtrip\u00eb n\u00eb vend t\u00eb nj\u00eb, si\u00e7 b\u00ebn QUIC.<\/p>\n

\"HTTP
\n
\nDuke qen\u00eb se QUIC kombinon z\u00ebvend\u00ebsimin e TCP-s\u00eb dhe implementimin e TLS 1.3, t\u00eb gjitha lidhjet jan\u00eb gjithmon\u00eb t\u00eb enkriptuara, dhe dekodimi i k\u00ebtij trafiku nuk \u00ebsht\u00eb m\u00eb i leht\u00eb sesa n\u00ebse do t\u00eb kalonte p\u00ebrmes HTTPS. P\u00ebr m\u00eb tep\u00ebr, QUIC \u00ebsht\u00eb implementuar n\u00eb nivelin aplikativ; z\u00ebvend\u00ebsimi i plot\u00eb i stack-ut t\u00eb TCP do t\u00eb kishte marr\u00eb pa fund<\/i>.<\/p>\n

Megjith\u00ebse mb\u00ebshtetje p\u00ebr shum\u00ebrenditje n\u00eb HTTP\/2, problemi i bllokimit t\u00eb radh\u00ebs s\u00eb par\u00eb mbetet p\u00ebr shkak t\u00eb nevoj\u00ebs p\u00ebr t\u00eb d\u00ebrguar paketat n\u00eb rend. QUIC \u00ebsht\u00eb implementuar mbi UDP, prandaj nuk ka bllokade n\u00eb parim, dhe p\u00ebr t\u00eb siguruar q\u00eb paketat t\u00eb mos humbasin p\u00ebrfundimisht, ato num\u00ebrohen dhe mund t\u00eb p\u00ebrmbajn\u00eb pjes\u00eb t\u00eb \"fqinjve\", duke siguruar mbivendosje. P\u00ebr m\u00eb tep\u00ebr, QUIC ndan radh\u00ebn monolitike n\u00eb disa m\u00ebngjyr\u00eb p\u00ebr lloje t\u00eb ndryshme k\u00ebrkesash brenda nj\u00eb lidhjeje. K\u00ebshtu, n\u00eb rast humbjeje t\u00eb nj\u00eb pakete, problemet mund t\u00eb ndodhin vet\u00ebm n\u00eb nj\u00eb radh\u00eb (p.sh., p\u00ebr transferimin e nj\u00eb skedari t\u00eb caktuar):<\/p>\n

\"HTTP
\n<\/p>\n

P\u00ebrdorimi <\/h2>\n

\nFillimisht, QUIC u zhvillua brenda Google dhe ishte kryesisht i optimizuar p\u00ebr p\u00ebrdorim brenda kompanis\u00eb. N\u00eb vitin 2013, ai u transferua n\u00eb IETF p\u00ebr standardizim (i cili vazhdon ende) dhe tani secili mund t\u00eb kontribuoj\u00eb n\u00eb p\u00ebrmir\u00ebsimin e protokollit, duke ofruar ato q\u00eb i mungojn\u00eb atij. Grupi i pun\u00ebs IETF organizon \u00e7do vit takime, ku miratohet standardi i ri dhe diskutohet p\u00ebr novacionet. Kjo realizim i QUIC konsiderohet si themelor, dhe baza p\u00ebr standardin HTTP\/3 \u00ebsht\u00eb pik\u00ebrisht kjo.<\/p>\n

Derisa t\u00eb p\u00ebrfundoj\u00eb, nuk flitet p\u00ebr p\u00ebrfshirjen e HTTP\/3 si protokollin kryesor, sepse \u00ebsht\u00eb akoma n\u00eb zhvillim dhe pothuajse nuk mb\u00ebshtetet:<\/p>\n

\"HTTP
\n
\nPor QUIC mund t\u00eb implementohet si nj\u00eb transport midis aplikacionit dhe serverit, q\u00eb Uber e ka realizuar me sukses:<\/p>\n

\n

Koment nga Uber mbi implementimin e QUIC<\/i><\/h3>\n

\nP\u00ebr t\u00eb integruar me sukses QUIC dhe p\u00ebr t\u00eb p\u00ebrmir\u00ebsuar performanc\u00ebn e aplikacionit n\u00eb kushte t\u00eb k\u00ebqija lidhjeje, ne z\u00ebvend\u00ebsuam stek\u00ebn e vjet\u00ebr (HTTP\/2 mbi TLS\/TCP) me protokollin QUIC. Ne angazhuam bibliotek\u00ebn rrjetore Cronet<\/a><\/noindex> nga Projeketet Chromium<\/a><\/noindex>, e cila p\u00ebrmban versionin origjinal, t\u00eb Google-it t\u00eb protokollit \u2013 gQUIC. Kjo implementim gjithashtu p\u00ebrmir\u00ebsohet vazhdimisht, p\u00ebr t\u00eb ndjekur specifikimin m\u00eb t\u00eb fundit t\u00eb IETF.<\/p>\n

Fillimisht, ne integrojm\u00eb Cronet n\u00eb aplikacionet tona Android, p\u00ebr t\u00eb shtuar mb\u00ebshtetje p\u00ebr QUIC. Integrimi u realizua n\u00eb m\u00ebnyr\u00eb q\u00eb t\u00eb ulin sa m\u00eb shum\u00eb kostot e migrimit. N\u00eb vend q\u00eb t\u00eb z\u00ebvend\u00ebsonim plot\u00ebsisht stek\u00ebn e vjet\u00ebr rrjetore, e cila p\u00ebrdorte bibliotek\u00ebn OkHttp<\/a><\/noindex>, ne integrojm\u00eb Cronet N\u00cb korniz\u00ebn e API-s\u00eb OkHttp. Duke kryer integrimin n\u00eb k\u00ebt\u00eb m\u00ebnyr\u00eb, shmang\u00ebm ndryshimet n\u00eb thirrjet tona rrjetore (t\u00eb cilat p\u00ebrdorin Retrofit<\/a><\/noindex>) n\u00eb nivelin API.<\/p>\n

N\u00eb p\u00ebrputhje me qasjen p\u00ebr pajisjet Android, ne implantuam Cronet n\u00eb aplikacionet Uber p\u00ebr iOS, duke kapur trafikun HTTP nga rrjeti API<\/a><\/noindex>, duke p\u00ebrdorur NSURLProtocol<\/a><\/noindex>. Kjo abstraksion, e ofruar nga iOS Foundation, p\u00ebrpunon t\u00eb dh\u00ebnat URL specifike p\u00ebr protokollin dhe garanton q\u00eb ne mund t\u00eb integrojm\u00eb Cronet n\u00eb aplikacionet tona iOS pa kosto t\u00eb konsiderueshme migrimi.<\/p><\/blockquote>\n

marr\u00eb nga k\u00ebtu<\/a><\/noindex> p\u00ebrkthimi i artikullit t\u00eb Uber<\/i><\/p>\n

N\u00eb backend, ata kapin lidhjet QUIC p\u00ebrmes Google Cloud lb, i cili mb\u00ebshtet protokollin<\/a><\/noindex> q\u00eb nga mesi i vitit 2018.<\/p>\n

Nuk \u00ebsht\u00eb nj\u00eb befasia q\u00eb Google Cloud funksionon mir\u00eb me protokollin e zhvilluar nga Google, por cilat jan\u00eb alternativat?<\/p>\n

Nginx<\/h3>\n

\nJo shum\u00eb koh\u00eb m\u00eb par\u00eb, CloudFlare provojn\u00eb t\u00eb bashkojn\u00eb<\/a><\/noindex> nginx (i cili p\u00ebr default nuk mb\u00ebshtet HTTP\/3) me mjetin e tij Quiche. Realizimi \u00ebsht\u00eb n\u00eb form\u00ebn e nj\u00eb skedari t\u00eb vet\u00ebm .patch, i shoq\u00ebruar me nj\u00eb tutorial p\u00ebr instalimin:<\/p>\n

curl -O https:\/\/nginx.org\/download\/nginx-1.16.1.tar.gz\ntar xvzf nginx-1.16.1.tar.gz\ngit clone --recursive https:\/\/github.com\/cloudflare\/quiche\ncd nginx-1.16.1\npatch -p01 < ..\/quiche\/extras\/nginx\/nginx-1.16.patch<\/code><\/pre>\n
\nK\u00ebtu mund t\u00eb lidhen modulat tuaja n\u00ebse \u00ebsht\u00eb e nevojshme<\/p>\n
.\/configure                          \t\n   \t--prefix=$PWD                       \t\n   \t--with-http_ssl_module              \t\n   \t--with-http_v2_module               \t\n   \t--with-http_v3_module               \t\n   \t--with-openssl=..\/quiche\/deps\/boringssl \n   \t--with-quiche=..\/quiche\n make<\/code><\/pre>\n
\nP\u00ebrfshin vet\u00ebm aktivizimin e mb\u00ebshtetjes p\u00ebr HTTP\/3<\/p>\n
events {\n    worker_connections  1024;\n}\n\nhttp {\n    server {\n        # Aktivizoni QUIC dhe HTTP\/3.\n        listen 443 quic reuseport;\n\n        # Aktivizoni HTTP\/2 (opsionale).\n        listen 443 ssl http2;\n\n        ssl_certificate      cert.crt;\n        ssl_certificate_key  cert.key;\n\n        # Aktivizoni t\u00eb gjitha versionet e TLS (TLSv1.3 k\u00ebrkohet p\u00ebr QUIC).\n        ssl_protocols TLSv1 TLSv1.1 TLSv1.2 TLSv1.3;\n\n        # K\u00ebrkesat e tamponit aktualisht nuk mb\u00ebshteten p\u00ebr HTTP\/3.\n        proxy_request_buffering off;\n\n        # Shtoni header Alt-Svc p\u00ebr t\u00eb negociuar HTTP\/3.\n        add_header alt-svc 'h3-27=":443"; ma=86400';\n    }\n}<\/code><\/pre>\n
\nN\u00eb browserat normal\u00eb, lidhja p\u00ebrmes HTTP\/3 nuk \u00ebsht\u00eb e mundur p\u00ebr momentin, por mund t\u00eb merrni Chrome Canary<\/a><\/noindex> dhe ta nisni at\u00eb me flagun --enable-quic<\/code>, t\u00eb adresoheni n\u00eb serverin tuaj ose, p\u00ebr shembull, n\u00eb faqen quic.rocks dhe t\u00eb shihni llojin e lidhjes n\u00eb Vegzat e Zhvilluesve:
\n\"HTTP
\nN\u00eb vend t\u00eb HTTP\/3 shkruhet http2+quic\/99<\/code>, por ndryshe \u00ebsht\u00eb pothuajse e nj\u00ebjt\u00eb.<\/p>\n
Teknologji t\u00eb tjera<\/h3>\n
<\/p>\n