Pas nj\u00eb vit zhvillimi, u publikua dega e re stabile e serverit HTTP me performanc\u00eb t\u00eb lart\u00eb dhe serverit proxy shum\u00ebprotokoll q\u00eb \u00ebsht\u00eb nginx 1.26.0, e cila p\u00ebrfshiu ndryshimet e akumuluara n\u00eb deg\u00ebn kryesore 1.25.x. N\u00eb vazhdim, t\u00eb gjitha ndryshimet n\u00eb deg\u00ebn e q\u00ebndrueshme 1.26 do t\u00eb lidhen me eliminimin e gabimeve t\u00eb r\u00ebnda dhe dob\u00ebsive. Shpejt do t\u00eb formohet dega kryesore nginx 1.27, n\u00eb t\u00eb cil\u00ebn do t\u00eb vazhdoj\u00eb zhvillimi i mund\u00ebsive t\u00eb reja. P\u00ebr p\u00ebrdoruesit e zakonsh\u00ebm, t\u00eb cil\u00ebt nuk kan\u00eb p\u00ebr detyr\u00eb t\u00eb sigurojn\u00eb pajtueshm\u00ebri me modul t\u00eb jasht\u00ebm, rekomandohet t\u00eb p\u00ebrdorin deg\u00ebn kryesore, mbi t\u00eb cil\u00ebn \u00e7do tre muaj formohen l\u00ebshime t\u00eb produktit komercial Nginx Plus. <\/p>\n
N\u00eb p\u00ebrputhje me raportin e marsit nga kompania Netcraft, rreth 243 milion faqe interneti jan\u00eb n\u00eb menaxhimin e nginx (nj\u00eb vit m\u00eb par\u00eb 289 milion). Nginx p\u00ebrdoret n\u00eb 18.15% t\u00eb t\u00eb gjitha faqeve aktive (nj\u00eb vit m\u00eb par\u00eb 18.94%, dy vite m\u00eb par\u00eb 20.08%), q\u00eb i korrespondon vendit t\u00eb dyt\u00eb n\u00eb k\u00ebt\u00eb kategori (pjesa p\u00ebr Apache \u00ebsht\u00eb 20.09% (nj\u00eb vit m\u00eb par\u00eb 20.52, dy vite m\u00eb par\u00eb 22.58%), Cloudflare \u2014 14.12% (11.32%, 10.42%), Google \u2014 10.41% (9.89%, 8.89%). Duke shqyrtuar t\u00eb gjitha faqet, nginx mban liderin dhe z\u00eb 22.31% t\u00eb tregut (nj\u00eb vit m\u00eb par\u00eb 25.94%, dy vite m\u00eb par\u00eb \u2014 31.13%), nd\u00ebrsa pjesa p\u00ebr Apache \u00ebsht\u00eb 20.17% (20.58, 23.08%), Cloudflare \u2014 11.24% (10.17, 5.49%), OpenResty (platform\u00eb bazuar n\u00eb nginx dhe LuaJIT) \u2014 7.93% (7.94%, 8.01%). <\/p>\n
Mes nj\u00eb milion nga situset m\u00eb t\u00eb vizituara n\u00eb bot\u00eb, pjesa e nginx arrin n\u00eb 20.63% (nj\u00eb vit m\u00eb par\u00eb 21.37%, dy vjet m\u00eb par\u00eb 21.79%), Cloudflare \u2014 22.59% (nj\u00eb vit m\u00eb par\u00eb 21.62%), Apache httpd \u2014 20.09% (21.18%). Sipas t\u00eb dh\u00ebnave nga W3Techs, nginx p\u00ebrdoret n\u00eb 34.3% t\u00eb situsve nga ata nj\u00eb milion m\u00eb t\u00eb vizituar, n\u00eb prillin e kaluar ky tregues ishte 34.5%, nd\u00ebrsa vitin e kaluar \u2014 33.1%. Pjesa e Apache ra nga 32.2% n\u00eb 30.1% brenda nj\u00eb viti, nd\u00ebrsa pjesa e Microsoft IIS ra nga 5.6% n\u00eb 4.8%. Pjesa e Node.js u rrit nga 2.4% n\u00eb 3.2%, nd\u00ebrsa pjesa e LiteSpeed nga 11.8% n\u00eb 12.9%. <\/p>\n
Moduli ngx_http_v3 me mb\u00ebshtetje eksperimentale p\u00ebr protokollin HTTP\/3 \u00ebsht\u00eb shtuar. P\u00ebr nd\u00ebrtimin e modulit \u00ebsht\u00eb parashikuar opsioni \u2014with-http_v3_module. HTTP\/3 p\u00ebrcakton p\u00ebrdorimin e protokollit QUIC (Quick UDP Internet Connections) si transport p\u00ebr HTTP\/2. QUIC \u00ebsht\u00eb nj\u00eb shtes\u00eb mbi protokollin UDP, q\u00eb mb\u00ebshtet shum\u00eb lidhje dhe ofron metoda kriptimi ekuivalente me TLS\/SSL. Protokolli u krijua n\u00eb vitin 2013 nga kompania Google si nj\u00eb alternativ\u00eb ndaj lidhjes TCP+TLS p\u00ebr Web, duke zgjidhur problemet me koh\u00ebn e gjat\u00eb t\u00eb vendosjes dhe pajtimit t\u00eb lidhjeve n\u00eb TCP dhe duke eliminuar vonesat nga humbja e paketave gjat\u00eb transmetimit t\u00eb t\u00eb dh\u00ebnave.\n
Kjo p\u00ebrfshin nj\u00eb direktiv\u00eb t\u00eb ve\u00e7ant\u00eb \u00abhttp2\u00bb p\u00ebr aktivizimin selektiv t\u00eb protokollit HTTP\/2 n\u00eb lidhje me server\u00ebt (mund t\u00eb p\u00ebrdoret n\u00eb blloqe t\u00eb ve\u00e7anta \u00abserver\u00bb). Parametri \u00abhttp2\u00bb n\u00eb direktiv\u00ebn \u00ablisten\u00bb \u00ebsht\u00eb shpallur i vjetruar.\n
Mbrojtja e forcuar kund\u00ebr aktiviteteve anomale t\u00eb klient\u00ebve HTTP\/2, sidomos ndaj sulmeve DoS t\u00eb klas\u00ebs \u00abRapid Reset\u00bb, ku krijohet nj\u00eb num\u00ebr i madh stream-esh q\u00eb ndalen p\u00ebrnj\u00ebher\u00eb brenda nj\u00eb lidhjeje HTTP\/2. N\u00eb konfigurimin e parazgjedhur, sulmet e tilla p\u00ebrplasen me kufirin e numrit t\u00eb k\u00ebrkesave p\u00ebr lidhjen \u00abkeepalive_requests\u00bb (pas \u00e7do 1000 k\u00ebrkesash lidhja do t\u00eb ndalet) dhe me kufizimet \u00ablimit_req\u00bb. P\u00ebr t\u00eb reaguar m\u00eb her\u00ebt ndaj flood-it t\u00eb k\u00ebrkesave p\u00ebrmes nj\u00eb numri t\u00eb madh stream-esh, \u00ebsht\u00eb shtuar nj\u00eb kufizim shtes\u00eb, i cili nuk lejon krijimin e m\u00eb shum\u00eb se 256 (2 * max_concurrent_streams) stream-eve t\u00eb reja n\u00eb \u00e7do cik\u00ebl t\u00eb p\u00ebrpunimit t\u00eb ngjarjeve. Ky kufizim i ri lejon fillimin e bllokimit t\u00eb k\u00ebrkesave para se t\u00eb arrihet kufiri i p\u00ebrgjithsh\u00ebm p\u00ebr numrin e stream-eve t\u00eb p\u00ebrgjithshme, p\u00ebr shembull, kur stream-et p\u00ebrpunohen asinkronisht ose ndalen.\n