{"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 - p\u00ebrdorimi i dobish\u00ebm i protokollit 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, i cili mb\u00ebshtet t\u00eb gjitha mund\u00ebsit\u00eb e TCP, TLS dhe HTTP\/2 dhe zgjidh shumic\u00ebn e problemeve t\u00eb tyre. Shpesh quhet nj\u00eb protokoll i ri ose \"eksperimental\", por ai ka kaluar prej koh\u00ebsh faz\u00ebn eksperimentale: zhvillimi i tij ka vazhduar p\u00ebr m\u00eb shum\u00eb se 7 vjet. Gjat\u00eb k\u00ebsaj kohe, protokolli nuk arriti t\u00eb b\u00ebhej standard, por gjithsesi ka marr\u00eb nj\u00eb shp\u00ebrndarje t\u00eb gjer\u00eb. P\u00ebr shembull, QUIC p\u00ebrdoret p\u00ebr t\u00eb p\u00ebrshpejtuar trafikun dhe p\u00ebr t\u00eb ulur vonesat n\u00eb rrjetet celulare nga gjigant\u00eb si Google dhe Facebook, nd\u00ebrsa IETF shpalli fork-un e tij si baz\u00eb p\u00ebr standardin HTTP\/3 (duke pasur parasysh se HTTP\/2 p\u00ebrdor vet\u00ebm 44.8%<\/a><\/noindex> t\u00eb faqeve).<\/a><\/noindex><\/p>\n

Koncepci<\/h2>\n

\nQUIC u zhvillua si nj\u00eb z\u00ebvend\u00ebsim p\u00ebr TCP-n\u00eb e vjet\u00ebruar, e cila fillimisht ishte e dizajnuar p\u00ebr rrjetet me tela me nj\u00eb p\u00ebrqindje t\u00eb ul\u00ebt humbjesh. TCP d\u00ebrgon paketat n\u00eb rend kronologjik, k\u00ebshtu q\u00eb n\u00eb rastin e humbjes s\u00eb nj\u00eb pakete, e gjith\u00eb radha ndalon (bllokimi i kok\u00ebs s\u00eb linj\u00ebs<\/a><\/noindex>), gj\u00eb q\u00eb ndikon negativisht n\u00eb cil\u00ebsin\u00eb dhe stabilitetin e lidhjes. P\u00ebr t\u00eb shmangur humbjet masive, rrjetet celulare p\u00ebrdorin mem\u00f3ria t\u00eb m\u00ebdha, \u00e7ka nga ana tjet\u00ebr \u00e7on n\u00eb tep\u00ebrsi dhe reagimin false negative t\u00eb protokollit (bufferbloat<\/a><\/noindex>). P\u00ebr m\u00eb tep\u00ebr, TCP shpenzon shum\u00eb koh\u00eb p\u00ebr t\u00eb vendosur nj\u00eb lidhje: k\u00ebrkesat SYN\/ACK dhe TLS shkojn\u00eb ve\u00e7mas, duke k\u00ebrkuar tre runde komunikimi 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 gjithmon\u00eb jan\u00eb t\u00eb enkriptuara, duke e b\u00ebr\u00eb t\u00eb v\u00ebshtir\u00eb dekodimin e k\u00ebtij trafiku, ashtu si\u00e7 do t\u00eb ishte p\u00ebr HTTPS. P\u00ebr m\u00eb tep\u00ebr, QUIC \u00ebsht\u00eb implementuar n\u00eb nivelin e aplikacionit, pasi nj\u00eb z\u00ebvend\u00ebsim i plot\u00eb i grupit t\u00eb TCP do t\u00eb k\u00ebrkonte p\u00ebrjet\u00ebsi<\/i>.<\/p>\n

Megjith\u00ebse mb\u00ebshtet shum\u00ebfishimin n\u00eb HTTP\/2, problemi i bllokimit t\u00eb kok\u00ebs s\u00eb linj\u00ebs mbetet p\u00ebr shkak t\u00eb nevoj\u00ebs p\u00ebr t\u00eb d\u00ebrguar paketat n\u00eb rend kronologjik. QUIC \u00ebsht\u00eb realizuar mbi UDP, k\u00ebshtu q\u00eb nuk ka bllokime n\u00eb parim, dhe p\u00ebr t\u00eb siguruar q\u00eb paketat nuk humbasin pa kthim, ato num\u00ebrohen dhe mund t\u00eb p\u00ebrmbajn\u00eb pjes\u00eb \"fqinji\", duke ofruar tep\u00ebrsi. P\u00ebr m\u00eb tep\u00ebr, QUIC ndan radh\u00ebn monolitike n\u00eb disa rrjedha p\u00ebr lloje t\u00eb ndryshme k\u00ebrkesash brenda nj\u00eb lidhjeje. K\u00ebshtu, n\u00eb rastin e humbjes s\u00eb nj\u00eb pakete, problemet mund t\u00eb shfaqen vet\u00ebm n\u00eb nj\u00eb radh\u00eb (p\u00ebr shembull, n\u00eb d\u00ebrgimin e nj\u00eb skedari t\u00eb caktuar):<\/p>\n

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

P\u00ebrdorimi <\/h2>\n

\nOriginally, QUIC was developed within Google, primarily for internal use. In 2013, it was handed over to the IETF for standardization (which is still ongoing), and now anyone can participate in the development of the protocol by suggesting what they feel is lacking. The IETF working group organizes annual meetings to ratify new standards and discuss innovations. This implementation of QUIC is considered the main one, and it is on this basis that the HTTP\/3 standard is certified.<\/p>\n

As of now, there is no talk of incorporating HTTP\/3 as the main protocol because it is still incomplete and has minimal support:<\/p>\n

\"HTTP
\n
\nHowever, QUIC can be implemented as a transport between an application and a server, as successfully done by Uber:<\/p>\n

\n

Uber's comment on the implementation of 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 stekun e vjeter (HTTP\/2 mbi TLS\/TCP) me protokollin QUIC. Ne p\u00ebrfshiu bibliotek\u00ebn e rrjetit Cronet<\/a><\/noindex> nga Projektet Chromium<\/a><\/noindex>, e cila p\u00ebrmban versionin origjinal t\u00eb protokollit t\u00eb Google, gQUIC. Kjo implementim gjithashtu p\u00ebrmir\u00ebsohet vazhdimisht p\u00ebr t'u p\u00ebrputhur me specifikimin m\u00eb t\u00eb fundit t\u00eb IETF.<\/p>\n

S\u00eb pari, ne integuam Cronet n\u00eb aplikacionet tona Android p\u00ebr t\u00eb shtuar mb\u00ebshtetje p\u00ebr QUIC. Integrimi u realizua n\u00eb nj\u00eb m\u00ebnyr\u00eb q\u00eb reduktonte sa m\u00eb shum\u00eb shpenzimet e migrimit. N\u00eb vend q\u00eb t\u00eb z\u00ebvend\u00ebsonim t\u00ebr\u00ebsisht stek\u00ebn e vjet\u00ebr t\u00eb rrjetit q\u00eb p\u00ebrdorte bibliotek\u00ebn OkHttp<\/a><\/noindex>, ne integuam Cronet N\u00cb kuad\u00ebr t\u00eb API-s\u00eb s\u00eb OkHttp. Duke e realizuar integrimin n\u00eb k\u00ebt\u00eb m\u00ebnyr\u00eb, ne shmanguam ndryshime n\u00eb thirrjet tona rrjetore (t\u00eb cilat p\u00ebrdorin Retrofit<\/a><\/noindex>) n\u00eb nivelin e API-s\u00eb.<\/p>\n

N\u00eb m\u00ebnyr\u00eb t\u00eb ngjashme me qasjen ton\u00eb p\u00ebr pajisjet Android, ne implementuam Cronet n\u00eb aplikacionet Uber p\u00ebr iOS, duke kapur trafik HTTP nga API<\/a><\/noindex>, duke p\u00ebrdorur NSURLProtocol<\/a><\/noindex>. Kjo abstraksion, e ofruar nga iOS Foundation, trajton t\u00eb dh\u00ebnat e URL-ve specifike p\u00ebr protokollin dhe garanton q\u00eb mund t\u00eb integrojm\u00eb Cronet n\u00eb aplikacionet tona p\u00ebr iOS pa shpenzime t\u00eb m\u00ebdha migrimi.<\/p><\/blockquote>\n

taken from this translation<\/a><\/noindex> of the Uber article<\/i><\/p>\n

On the backend, they were capturing QUIC connections through Google Cloud lb, which supports the protocol<\/a><\/noindex> since mid-2018.<\/p>\n

It's no surprise that Google Cloud works perfectly with a protocol developed by Google, but what are the alternatives?<\/p>\n

Nginx<\/h3>\n

\nRecently, CloudFlare attempted to combine<\/a><\/noindex> nginx (which by default does not support HTTP\/3) with its tool Quiche. The implementation is available as a single .patch file, along with an installation tutorial:<\/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
\nHere, you can include your own modules if needed<\/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
\nAll that remains is to enable HTTP\/3 support<\/p>\n
events {\n    worker_connections  1024;\n}\n\nhttp {\n    server {\n        # Aktivizo QUIC dhe HTTP\/3.\n        listen 443 quic reuseport;\n\n        # Aktivizo HTTP\/2 (opcional).\n        listen 443 ssl http2;\n\n        ssl_certificate      cert.crt;\n        ssl_certificate_key  cert.key;\n\n        # Aktivizo 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        # Bufetimi i k\u00ebrkesave nuk mb\u00ebshtetet aktualisht p\u00ebr HTTP\/3.\n        proxy_request_buffering off;\n\n        # Shto header-in Alt-Svc p\u00ebr t\u00eb negociuar HTTP\/3.\n        add_header alt-svc 'h3-27=\":443\"; ma=86400';\n    }\n}<\/code><\/pre>\n
\nIn standard browsers, connecting via HTTP\/3 is not currently possible, but you can take Chrome Canary<\/a><\/noindex> and run it with the flag --enable-quic<\/code>, access your server or, for example, the site quic.rocks and check the connection type in Developer Tools:
\n\"HTTP
\nInstead of HTTP\/3, it shows http2+quic\/99<\/code>, but essentially, it's the same thing.<\/p>\n
Other technologies<\/h3>\n
<\/p>\n