{"id":794,"date":"2026-09-17T12:31:50","date_gmt":"2026-09-17T12:31:50","guid":{"rendered":"https:\/\/www.vps.tc\/blog\/?p=794"},"modified":"2026-09-17T10:20:04","modified_gmt":"2026-09-17T10:20:04","slug":"what-is-quic-faster-internet-protocol","status":"publish","type":"post","link":"https:\/\/www.vps.tc\/blog\/en\/what-is-quic-faster-internet-protocol\/","title":{"rendered":"What Is QUIC? A Guide to the Faster Internet Protocol"},"content":{"rendered":"<div class=\"aiw-summary\" id=\"aiw-ozet\">\n<p class=\"aiw-summary-title\">Quick Summary &#8211; QUIC<\/p>\n<p>QUIC, UDP \u00fczerinde \u00e7al\u0131\u015fan ve HTTP\/3 taraf\u0131ndan kullan\u0131lan g\u00fcvenli bir ta\u015f\u0131ma protokol\u00fcd\u00fcr. Ba\u011f\u0131ms\u0131z ak\u0131\u015flar\u0131, entegre TLS 1.3 el s\u0131k\u0131\u015fmas\u0131 ve ba\u011flant\u0131 ta\u015f\u0131nmas\u0131 kay\u0131pl\u0131 veya de\u011fi\u015fken a\u011flarda yard\u0131mc\u0131 olabilir; TCP geri d\u00f6n\u00fc\u015f\u00fc ve ger\u00e7ek \u00f6l\u00e7\u00fcm yine gereklidir.<\/p>\n<ul>\n<li><strong>Ta\u015f\u0131ma katman\u0131<\/strong> \u2014 QUIC, UDP \u00fczerinde \u00e7al\u0131\u015f\u0131rken g\u00fcvenilirlik, s\u0131ralama, kay\u0131p kurtarma ve t\u0131kan\u0131kl\u0131k kontrol\u00fc sa\u011flar.<\/li>\n<li><strong>HTTP\/3 ili\u015fkisi<\/strong> \u2014 HTTP\/3, QUIC&#039;i kullanan HTTP protokol\u00fcd\u00fcr; iki ad farkl\u0131 katmanlar\u0131 tan\u0131mlar.<\/li>\n<li><strong>Paket kayb\u0131<\/strong> \u2014 Ba\u011f\u0131ms\u0131z QUIC ak\u0131\u015flar\u0131, HTTP\/2&#039;nin TCP \u00fczerindeki \u00e7oklamas\u0131na k\u0131yasla paket kayb\u0131n\u0131n etkisini s\u0131n\u0131rlayabilir.<\/li>\n<li><strong>A\u011f de\u011fi\u015fiklikleri<\/strong> \u2014 Connection ID de\u011ferleri, istemcinin a\u011f de\u011fi\u015ftirirken hemen yeni ba\u011flant\u0131 kurmadan devam etmesine yard\u0131mc\u0131 olabilir.<\/li>\n<li><strong>Sunucu portlar\u0131<\/strong> \u2014 HTTP\/3 normalde UDP 443 kullan\u0131r; HTTP\/2 ve HTTP\/1.1 geri d\u00f6n\u00fc\u015f\u00fc i\u00e7in TCP 443 a\u00e7\u0131k kalmal\u0131d\u0131r.<\/li>\n<li><strong>Test<\/strong> \u2014 DNS&#039;i, UDP g\u00fcvenlik duvar\u0131 eri\u015fimini, curl deste\u011fini, taray\u0131c\u0131 protokol\u00fcn\u00fc, gecikmeyi, hatalar\u0131 ve geri d\u00f6n\u00fc\u015f oran\u0131n\u0131 kontrol edin.<\/li>\n<\/ul>\n<\/div>\n<p class=\"aiw-lead\">QUIC, UDP \u00fczerinde \u00e7al\u0131\u015fan g\u00fcvenli bir ta\u015f\u0131ma protokol\u00fcd\u00fcr; TCP&#039;den bekledi\u011finiz g\u00fcvenilirlik, ak\u0131\u015f y\u00f6netimi ve t\u0131kan\u0131kl\u0131k kontrol\u00fcn\u00fc kendi katman\u0131nda sa\u011flar. HTTP\/3, ba\u011f\u0131ms\u0131z ak\u0131\u015flar ve TLS 1.3 entegrasyonu sayesinde baz\u0131 a\u011flarda ta\u015f\u0131ma gecikmesini azaltabilir; ancak \u00f6l\u00e7\u00fcm ve TCP geri d\u00f6n\u00fc\u015f\u00fc h\u00e2l\u00e2 \u015fartt\u0131r.<\/p>\n<div class=\"aiw-toc\" style=\"border:1px solid #dbe3ea;border-radius:8px;padding:16px 20px;margin:0 0 28px\">\n<p class=\"aiw-toc-head\"><strong>Table of Contents<\/strong><span class=\"aiw-toc-meta\"> \u00b7 12 min read<\/span><\/p>\n<ol style=\"margin:10px 0 0;padding-left:22px\">\n<li><a href=\"#quic-nedir-hangi-sorunu-cozer\">QUIC nedir, hangi sorunu \u00e7\u00f6zer?<\/a><\/li>\n<li><a href=\"#quic-nasil-calisir\">QUIC nas\u0131l \u00e7al\u0131\u015f\u0131r?<\/a><\/li>\n<li><a href=\"#quic-tcp-ve-http-2-karsilastirmasi\">QUIC, TCP ve HTTP\/2 kar\u015f\u0131la\u015ft\u0131rmas\u0131<\/a><\/li>\n<li><a href=\"#http-3-ile-quic-arasindaki-iliski-nedir\">HTTP\/3 ile QUIC aras\u0131ndaki ili\u015fki nedir?<\/a><\/li>\n<li><a href=\"#sunucuda-http-3-ve-quic-testi\">Sunucuda HTTP\/3 ve QUIC testi<\/a><\/li>\n<li><a href=\"#quic-icin-portlar-ve-guvenlik-duvari-kurallari\">QUIC i\u00e7in portlar ve g\u00fcvenlik duvar\u0131 kurallar\u0131<\/a><\/li>\n<li><a href=\"#quic-bir-siteyi-ne-zaman-gercekten-hizlandirir\">QUIC bir siteyi ne zaman ger\u00e7ekten h\u0131zland\u0131r\u0131r?<\/a><\/li>\n<li><a href=\"#quic-sinirlamalari-ve-guvenlik-noktalari\">QUIC s\u0131n\u0131rlamalar\u0131 ve g\u00fcvenlik noktalar\u0131<\/a><\/li>\n<li><a href=\"#uygulanabilir-bir-quic-gecis-plani\">Uygulanabilir bir QUIC ge\u00e7i\u015f plan\u0131<\/a><\/li>\n<li><a href=\"#http-3u-acmadan-once-bunlari-kontrol-edin\">HTTP\/3&#039;\u00fc A\u00e7madan \u00d6nce Bunlar\u0131 Kontrol Edin<\/a><\/li>\n<li><a href=\"#frequently-asked-questions\">Frequently Asked Questions<\/a><\/li>\n<li><a href=\"#sources\">Sources<\/a><\/li>\n<\/ol>\n<\/div>\n<h2 id=\"quic-nedir-hangi-sorunu-cozer\">QUIC nedir, hangi sorunu \u00e7\u00f6zer?<\/h2>\n<p>QUIC, uygulama trafi\u011fini UDP \u00fczerinden ta\u015f\u0131yan ve ba\u011flant\u0131 kurulumu ile TLS 1.3 \u015fifrelemesini birlikte tasarlayan modern bir ta\u015f\u0131ma protokol\u00fcd\u00fcr. IETF&#8217;nin yay\u0131mlad\u0131\u011f\u0131 RFC 9000; ak\u0131\u015flar\u0131n \u00e7oklanmas\u0131, ba\u011flant\u0131 kimlikleri, paket kayb\u0131 kurtarma ve ba\u011flant\u0131 ta\u015f\u0131nmas\u0131 gibi \u00f6zellikleri tan\u0131mlar. HTTP\/3 ise QUIC \u00fczerinde \u00e7al\u0131\u015fan HTTP s\u00fcr\u00fcm\u00fcd\u00fcr.<\/p>\n<p>Bu ayr\u0131m pratikte \u00f6nemlidir. QUIC ta\u015f\u0131ma katman\u0131d\u0131r; HTTP\/3 bu ta\u015f\u0131ma katman\u0131n\u0131 kullanan HTTP protokol\u00fcd\u00fcr. Bir web sunucusunda HTTP\/3&#8217;\u00fc etkinle\u015ftirdi\u011finizde genellikle UDP 443 \u00fczerinden QUIC&#8217;i, TCP 443 \u00fczerinden de HTTP\/2 veya HTTP\/1.1&#8217;i birlikte sunars\u0131n\u0131z.<\/p>\n<p>TCP onlarca y\u0131ld\u0131r g\u00fcvenilir bir temel sa\u011fl\u0131yor. Fakat TCP ba\u011flant\u0131s\u0131 i\u00e7indeki tek bir kay\u0131p paket, ayn\u0131 ba\u011flant\u0131daki b\u00fct\u00fcn veri ak\u0131\u015flar\u0131n\u0131 etkileyebilir. QUIC veriyi ba\u011f\u0131ms\u0131z ak\u0131\u015flara b\u00f6ler. Bir ak\u0131\u015fta paket kayb\u0131 oldu\u011funda di\u011fer ak\u0131\u015flar\u0131n bu paketin yeniden g\u00f6nderilmesini beklemesi gerekmez.<\/p>\n<p><strong>Ne yapmal\u0131?<\/strong> QUIC&#8217;i HTTP\/3 ile birlikte de\u011ferlendirin ve sunucu yap\u0131land\u0131r\u0131rken ta\u015f\u0131ma katman\u0131 ile HTTP katman\u0131n\u0131n g\u00f6revlerini birbirine kar\u0131\u015ft\u0131rmay\u0131n.<\/p>\n<h2 id=\"quic-nasil-calisir\">QUIC nas\u0131l \u00e7al\u0131\u015f\u0131r?<\/h2>\n<p>QUIC d\u0131\u015far\u0131dan basit g\u00f6r\u00fcnebilir; sonu\u00e7ta UDP kullan\u0131r. \u0130\u00e7eride ise TCP&#8217;nin y\u0131llar i\u00e7inde biriktirdi\u011fi g\u00fcvenilirlik, s\u0131ralama, ak\u0131\u015f y\u00f6netimi, t\u0131kan\u0131kl\u0131k kontrol\u00fc ve kay\u0131p kurtarma i\u015flerinin \u00f6nemli b\u00f6l\u00fcm\u00fcn\u00fc kullan\u0131c\u0131 alan\u0131nda yeniden uygular. TLS 1.3 de ba\u011flant\u0131 el s\u0131k\u0131\u015fmas\u0131na do\u011frudan dahil edilir.<\/p>\n<p>Kula\u011fa uzun geliyor. Mant\u0131\u011f\u0131 asl\u0131nda net.<\/p>\n<h3>UDP \u00fczerinde g\u00fcvenilir ta\u015f\u0131ma<\/h3>\n<p>UDP teslimat veya paket s\u0131ralamas\u0131 garantisi vermez. QUIC bu bo\u015flu\u011fu paket numaralar\u0131, onaylar ve kay\u0131p kurtarma algoritmalar\u0131yla doldurur. Bu y\u00fczden &#8220;UDP kulland\u0131\u011f\u0131 i\u00e7in QUIC g\u00fcvenilir de\u011fildir&#8221; c\u00fcmlesi eksiktir: g\u00fcvenilirli\u011fi UDP de\u011fil, QUIC sa\u011flar.<\/p>\n<p>QUIC paketleri i\u015fletim sisteminin \u00e7ekirdek TCP y\u0131\u011f\u0131n\u0131na do\u011frudan ba\u011fl\u0131 de\u011fildir. Bir uygulama veya k\u00fct\u00fcphane, her i\u015fletim sisteminin ve a\u011f cihaz\u0131n\u0131n yeni bir TCP \u00f6zelli\u011fini desteklemesini beklemeden protokol davran\u0131\u015f\u0131n\u0131 g\u00fcncelleyebilir. Bu, her g\u00fcncellemenin kolay olaca\u011f\u0131 anlam\u0131na gelmez; geli\u015ftiricilere daha geni\u015f bir hareket alan\u0131 verir.<\/p>\n<h3>Ba\u011flant\u0131 kimlikleri ve a\u011f de\u011fi\u015fiklikleri<\/h3>\n<p>TCP ba\u011flant\u0131lar\u0131 genellikle istemci IP adresi, istemci portu, sunucu IP adresi ve sunucu portundan olu\u015fan d\u00f6rt \u00f6\u011feyle tan\u0131mlan\u0131r. Bir cihaz Wi-Fi&#8217;dan mobil a\u011fa ge\u00e7ti\u011finde bu bilgiler de\u011fi\u015febilir ve TCP ba\u011flant\u0131s\u0131 kopabilir.<\/p>\n<p>QUIC ba\u011flant\u0131lar\u0131 bunun yerine Connection ID de\u011ferleriyle takip edilebilir. \u0130stemci a\u011f de\u011fi\u015ftirirken ayn\u0131 ba\u011flant\u0131y\u0131 koruyabilir; bu da mobil cihazlarda veya Wi-Fi kapsamas\u0131n\u0131n s\u0131k de\u011fi\u015fti\u011fi yerlerde yeniden ba\u011flanma maliyetini azaltabilir. Bu bir garanti de\u011fildir. NAT, g\u00fcvenlik duvarlar\u0131 ve sunucu politikas\u0131 h\u00e2l\u00e2 sonucu belirler.<\/p>\n<p>Ben bunu \u00f6zellikle hareket halindeyken anlaml\u0131 buluyorum. Ancak protokol\u00fcn ad\u0131 tek ba\u015f\u0131na kopan bir mobil ba\u011flant\u0131y\u0131 iyile\u015ftirmez.<\/p>\n<h3>Ak\u0131\u015flar ve head-of-line blocking<\/h3>\n<p>HTTP\/2, tek bir TCP ba\u011flant\u0131s\u0131 \u00fczerinde birden fazla istek ve yan\u0131t\u0131 \u00e7oklar. Bu ba\u011flant\u0131 say\u0131s\u0131n\u0131 azalt\u0131r; fakat kay\u0131p bir TCP paketi, ondan sonraki verilerin paket yeniden g\u00f6nderilene kadar beklemesine yol a\u00e7abilir. Buna head-of-line blocking denir.<\/p>\n<p>QUIC \u00e7oklamay\u0131 ta\u015f\u0131ma katman\u0131na ta\u015f\u0131r. HTTP\/3 ba\u011flant\u0131s\u0131ndaki her istek kendi QUIC ak\u0131\u015f\u0131n\u0131 kullanabilir. Bir g\u00f6rsel ak\u0131\u015f\u0131 paket kayb\u0131 nedeniyle beklerken CSS veya API ak\u0131\u015f\u0131 ilerleyebilir. Kay\u0131p paket yine yeniden g\u00f6nderilir; gecikme daha \u00e7ok etkilenen ak\u0131\u015fla s\u0131n\u0131rl\u0131 kal\u0131r.<\/p>\n<h2 id=\"quic-tcp-ve-http-2-karsilastirmasi\">QUIC, TCP ve HTTP\/2 kar\u015f\u0131la\u015ft\u0131rmas\u0131<\/h2>\n<p>Kar\u015f\u0131la\u015ft\u0131rmay\u0131 &#8220;UDP daha h\u0131zl\u0131d\u0131r&#8221; c\u00fcmlesine indirgemek do\u011fru olmaz. QUIC&#8217;in olas\u0131 avantaj\u0131; UDP&#8217;nin datagram modelini TLS 1.3, ak\u0131\u015f y\u00f6netimi, ba\u011flant\u0131 kontrol\u00fc ve kay\u0131p kurtarmayla birlikte kullanmas\u0131ndan gelir.<\/p>\n<table>\n<thead>\n<tr>\n<th>\u00d6zellik<\/th>\n<th>TCP + TLS + HTTP\/2<\/th>\n<th>QUIC + HTTP\/3<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Temel ta\u015f\u0131ma<\/td>\n<td>TCP, genellikle TCP 443<\/td>\n<td>UDP, genellikle UDP 443<\/td>\n<\/tr>\n<tr>\n<td>TLS entegrasyonu<\/td>\n<td>TCP ba\u011flant\u0131s\u0131ndan sonra ayr\u0131 TLS el s\u0131k\u0131\u015fmas\u0131<\/td>\n<td>TLS 1.3, QUIC el s\u0131k\u0131\u015fmas\u0131yla entegre<\/td>\n<\/tr>\n<tr>\n<td>\u00c7oklama<\/td>\n<td>TCP \u00fczerinde HTTP\/2 ak\u0131\u015flar\u0131<\/td>\n<td>Ta\u015f\u0131ma katman\u0131nda QUIC ak\u0131\u015flar\u0131<\/td>\n<\/tr>\n<tr>\n<td>Paket kayb\u0131n\u0131n etkisi<\/td>\n<td>TCP ba\u011flant\u0131s\u0131ndaki ak\u0131\u015flar\u0131 etkileyebilir<\/td>\n<td>\u00d6ncelikle ilgili ak\u0131\u015f\u0131 etkiler<\/td>\n<\/tr>\n<tr>\n<td>A\u011f de\u011fi\u015fiklikleri<\/td>\n<td>Yeni TCP ba\u011flant\u0131s\u0131 gerekebilir<\/td>\n<td>Connection ID sayesinde m\u00fcmk\u00fcn olabilir<\/td>\n<\/tr>\n<tr>\n<td>Sunucu eri\u015fimi<\/td>\n<td>TCP 443<\/td>\n<td>UDP 443; TCP geri d\u00f6n\u00fc\u015f\u00fc a\u00e7\u0131k kalmal\u0131<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>RFC 9001, QUIC&#8217;in TLS 1.3&#8217;\u00fc nas\u0131l kulland\u0131\u011f\u0131n\u0131 tan\u0131mlar. QUIC eski bir TLS s\u00fcr\u00fcm\u00fcyle \u00e7al\u0131\u015facak veya \u015fifreleme sonradan eklenecek \u015fekilde tasarlanmam\u0131\u015ft\u0131r. Sertifika y\u00f6netimi yine \u00f6nemlidir: HTTPS sertifikalar\u0131, alan adlar\u0131 ve istemci kimlik do\u011frulamas\u0131 HTTP\/3 kulland\u0131\u011f\u0131n\u0131zda ortadan kalkmaz.<\/p>\n<p>\u0130lk ba\u011flant\u0131n\u0131n her zaman dramatik bi\u00e7imde h\u0131zlanaca\u011f\u0131n\u0131 varsaymay\u0131n. \u0130stemci sunucuya yak\u0131nsa, a\u011f yolu sa\u011flamsa ve TLS oturum yeniden kullan\u0131m\u0131 \u00e7al\u0131\u015f\u0131yorsa TCP ile HTTP\/2 zaten yeterince h\u0131zl\u0131 olabilir. Sonu\u00e7; el s\u0131k\u0131\u015fma maliyetine, paket kayb\u0131na, a\u011f de\u011fi\u015fikliklerine ve paralel isteklerin yap\u0131s\u0131na ba\u011fl\u0131d\u0131r.<\/p>\n<p><strong>Ne yapmal\u0131?<\/strong> UDP 443&#8217;\u00fc eklerken TCP 443&#8217;\u00fc a\u00e7\u0131k b\u0131rak\u0131n ve ger\u00e7ek HTTP\/2 ile HTTP\/3 istemci davran\u0131\u015f\u0131n\u0131 ayr\u0131 ayr\u0131 \u00f6l\u00e7\u00fcn.<\/p>\n<h2 id=\"http-3-ile-quic-arasindaki-iliski-nedir\">HTTP\/3 ile QUIC aras\u0131ndaki ili\u015fki nedir?<\/h2>\n<p>HTTP\/3, RFC 9114 ile tan\u0131mlanan ve QUIC \u00fczerinde \u00e7al\u0131\u015fan HTTP s\u00fcr\u00fcm\u00fcd\u00fcr. HTTP metotlar\u0131, durum kodlar\u0131, ba\u015fl\u0131klar ve istek g\u00f6vdeleri tan\u0131d\u0131k kal\u0131r; as\u0131l de\u011fi\u015fiklik bu mesajlar\u0131n a\u011f \u00fczerinde nas\u0131l ta\u015f\u0131nd\u0131\u011f\u0131d\u0131r.<\/p>\n<p>HTTP\/2, ba\u015fl\u0131klar\u0131 HPACK ile s\u0131k\u0131\u015ft\u0131r\u0131r. HTTP\/3 ise QUIC&#8217;in ba\u011f\u0131ms\u0131z ak\u0131\u015f modeline g\u00f6re tasarlanan QPACK&#8217;i kullan\u0131r. Ama\u00e7, ba\u015fl\u0131k s\u0131k\u0131\u015ft\u0131rma tablosundaki bir g\u00fcncellemenin ilgisiz ak\u0131\u015flar\u0131 gereksiz yere durdurmas\u0131n\u0131 \u00f6nlemektir.<\/p>\n<p>Taray\u0131c\u0131lar bir sunucunun HTTP\/3 destekledi\u011fini \u00e7o\u011funlukla <code>Alt-Svc<\/code> yan\u0131t ba\u015fl\u0131\u011f\u0131 veya HTTPS DNS kayd\u0131 \u00fczerinden \u00f6\u011frenir. \u0130lk istek TCP ile gidebilir; ard\u0131ndan istemci UDP 443 \u00fczerinden QUIC ba\u011flant\u0131s\u0131n\u0131 deneyebilir. UDP \u00e7al\u0131\u015fm\u0131yorsa TCP tabanl\u0131 HTTP\/2&#8217;ye d\u00f6nmek, ge\u00e7i\u015f s\u00fcrecindeki altyap\u0131 i\u00e7in sa\u011fl\u0131kl\u0131 davran\u0131\u015ft\u0131r.<\/p>\n<p>HTTP\/3 kullanmak uygulamada otomatik olarak de\u011fi\u015fiklik yapman\u0131z\u0131 gerektirmez. PHP, Node.js veya Python uygulaman\u0131z HTTP isteklerini almaya devam edebilir. Pek \u00e7ok kurulumda QUIC, ziyaret\u00e7iye bakan reverse proxy&#8217;de sonland\u0131r\u0131l\u0131r; proxy ile uygulama sunucusu aras\u0131ndaki ba\u011flant\u0131 HTTP\/1.1 veya HTTP\/2 olarak kalabilir.<\/p>\n<h2 id=\"sunucuda-http-3-ve-quic-testi\">Sunucuda HTTP\/3 ve QUIC testi<\/h2>\n<p>\u00d6nce alan ad\u0131n\u0131n do\u011fru adrese \u00e7\u00f6z\u00fcmlendi\u011fini ve sunucunun UDP 443 \u00fczerinde dinledi\u011fini kontrol edin. <em><a href=\"https:\/\/www.vps.tc\/blog\/en\/what-is-an-ip-address-and-how-does-it-work\/\">What Is an IP Address and How Does It Work?<\/a><\/em> yaz\u0131s\u0131ndaki temel kontroller burada da i\u015finize yarar; yaln\u0131z \u00e7al\u0131\u015fan TCP eri\u015fimi, UDP eri\u015fiminin \u00e7al\u0131\u015ft\u0131\u011f\u0131n\u0131 kan\u0131tlamaz.<\/p>\n<pre><code>dig +short A example.com\ndig +short AAAA example.com\nss -lunp | grep ':443'\nsudo nft list ruleset<\/code><\/pre>\n<p>\u0130lk iki komut IPv4 ve IPv6 kay\u0131tlar\u0131n\u0131 g\u00f6sterir. <code>ss<\/code> \u00e7\u0131kt\u0131s\u0131 UDP 443 \u00fczerinde bir s\u00fcrecin dinleyip dinlemedi\u011fini, <code>nft<\/code> ise g\u00fcvenlik duvar\u0131 kurallar\u0131n\u0131 g\u00f6sterir. Yaln\u0131zca TCP 443 g\u00f6r\u00fcyorsan\u0131z HTTP\/3 hen\u00fcz dinlemiyor olabilir.<\/p>\n<p>Benim OptiPlex \u00fczerindeki Proxmox laboratuvar\u0131mda bu kontrolleri \u00f6zellikle ayr\u0131 \u00e7al\u0131\u015ft\u0131r\u0131yorum. Bir keresinde hizmetin \u00e7al\u0131\u015ft\u0131\u011f\u0131n\u0131 g\u00f6r\u00fcnce a\u011f yolunu tamamlanm\u0131\u015f sand\u0131m; istemci testinde UDP kural\u0131n\u0131n eksik oldu\u011funu fark ettim. Dinleyen soket, \u00e7al\u0131\u015fan eri\u015fim yolu demek de\u011fil.<\/p>\n<p>curl derlemeniz HTTP\/3 destekliyorsa basit bir istemci iste\u011fi deneyin:<\/p>\n<pre><code>curl -I --http3 https:\/\/example.com<\/code><\/pre>\n<p>Bu komutun \u00e7al\u0131\u015fmas\u0131, curl&#8217;\u00fcn HTTP\/3 destekleyen bir QUIC k\u00fct\u00fcphanesiyle derlenmi\u015f olmas\u0131n\u0131 gerektirir. <code>option --http3: the installed libcurl version doesn't support this<\/code> benzeri bir hata sunucunun bozuk oldu\u011funu kan\u0131tlamaz. \u00d6nce istemci yetene\u011fini kontrol edin.<\/p>\n<pre><code>curl -V<\/code><\/pre>\n<p><code>Features<\/code> sat\u0131r\u0131nda HTTP3 veya HTTP\/3 deste\u011fiyle ili\u015fkili bir \u00f6zellik aray\u0131n. Da\u011f\u0131t\u0131m\u0131n\u0131z\u0131n curl paketi bunu i\u00e7ermiyorsa taray\u0131c\u0131 geli\u015ftirici ara\u00e7lar\u0131n\u0131, <code>nghttp3<\/code> tabanl\u0131 bir istemciyi veya sa\u011flay\u0131c\u0131n\u0131z\u0131n resmi test arac\u0131n\u0131 kullanabilirsiniz.<\/p>\n<p>Taray\u0131c\u0131da Network panelindeki Protocol s\u00fctununa bak\u0131n. <code>h3<\/code> veya <code>h3-29<\/code> HTTP\/3&#8217;\u00fc, <code>h2<\/code> HTTP\/2&#8217;yi, <code>http\/1.1<\/code> ise eski protokol\u00fc g\u00f6sterir. \u00d6nbellek ve mevcut oturum ilk testi etkileyebilir; \u00f6zel pencere veya yeni profil ile de deneyin.<\/p>\n<p><strong>Ne yapmal\u0131?<\/strong> curl deste\u011fini, DNS kay\u0131tlar\u0131n\u0131, UDP 443 g\u00fcvenlik duvar\u0131 kural\u0131n\u0131 ve taray\u0131c\u0131n\u0131n anla\u015f\u0131lm\u0131\u015f protokol\u00fcn\u00fc tek bir test plan\u0131n\u0131n par\u00e7alar\u0131 olarak do\u011frulay\u0131n.<\/p>\n<div class=\"aiw-callout aiw-callout-tip\">\n<p class=\"aiw-callout-label\">Tip<\/p>\n<p>UDP&#039;yi TCP&#039;den ba\u011f\u0131ms\u0131z test edin. TCP 443&#039;e ba\u015far\u0131l\u0131 ba\u011flant\u0131 kurman\u0131z, sa\u011flay\u0131c\u0131 g\u00fcvenlik duvar\u0131, host g\u00fcvenlik duvar\u0131 ve a\u011f yolu \u00fczerinden UDP 443&#039;\u00fcn eri\u015filebilir oldu\u011funu g\u00f6stermez.<\/p>\n<\/div>\n<h2 id=\"quic-icin-portlar-ve-guvenlik-duvari-kurallari\">QUIC i\u00e7in portlar ve g\u00fcvenlik duvar\u0131 kurallar\u0131<\/h2>\n<p>HTTP\/3 i\u00e7in kullan\u0131lan standart sunucu portu genellikle UDP 443&#8217;t\u00fcr. HTTP\/2 ve HTTP\/1.1 geri d\u00f6n\u00fc\u015f\u00fc i\u00e7in TCP 443 a\u00e7\u0131k kalmal\u0131d\u0131r. QUIC istemcileri tek bir sabit kaynak portu kullanmaz; i\u015fletim sistemi normalde ge\u00e7ici bir UDP portu se\u00e7er.<\/p>\n<p>VPS sa\u011flay\u0131c\u0131s\u0131n\u0131n security group&#8217;u UDP 443&#8217;\u00fc engelliyorsa Nginx&#8217;te veya uygulama sunucusunda QUIC&#8217;i a\u00e7mak yetmez. \u0130\u015fletim sistemi g\u00fcvenlik duvar\u0131n\u0131, bulut g\u00fcvenlik grubunu, edge proxy&#8217;yi, CDN&#8217;i ve kurumsal a\u011f cihazlar\u0131n\u0131 ayr\u0131 ayr\u0131 kontrol edin.<\/p>\n<p>UDP&#8217;yi s\u0131n\u0131rs\u0131z b\u0131rakmak da g\u00fcvenlik politikas\u0131 de\u011fildir. Paket h\u0131z\u0131n\u0131, ba\u011flant\u0131 say\u0131s\u0131n\u0131 ve kaynak t\u00fcketimini izleyin. QUIC el s\u0131k\u0131\u015fmalar\u0131 ve \u015fifreleme i\u015flemleri CPU kullanabilir. DDoS korumas\u0131na ihtiya\u00e7 duyan projelerde <em><a href=\"https:\/\/www.vps.tc\/blog\/en\/what-is-a-ddos-attack-vps-protection-guide\/\">What Is a DDoS Attack? A Practical VPS Protection Guide<\/a><\/em> yaz\u0131s\u0131ndaki a\u011f kontrollerine UDP taraf\u0131n\u0131 da eklemek gerekir.<\/p>\n<p>MTU ve par\u00e7alanmay\u0131 da g\u00f6z ard\u0131 etmeyin. Par\u00e7alanm\u0131\u015f UDP paketleri, TCP&#8217;deki ar\u0131zalardan farkl\u0131 \u015fekilde ba\u015far\u0131s\u0131z olabilir. T\u00fcnel, VPN veya ba\u015fka bir encapsulation kullan\u0131yorsan\u0131z yol MTU davran\u0131\u015f\u0131n\u0131 ve paket kayb\u0131n\u0131 g\u00f6zlemleyin.<\/p>\n<p>K\u00fc\u00e7\u00fck bir kural de\u011fi\u015fikli\u011fi bile sonu\u00e7 verir. \u00d6nce staging&#8217;de deneyin.<\/p>\n<div class=\"aiw-callout aiw-callout-warn\">\n<p class=\"aiw-callout-label\">Caution<\/p>\n<p>HTTP\/3&#039;\u00fc a\u00e7t\u0131ktan sonra TCP 443&#039;\u00fc kald\u0131rmay\u0131n. Baz\u0131 istemciler ve a\u011flar QUIC kullanamaz; \u00e7al\u0131\u015fan TCP geri d\u00f6n\u00fc\u015f\u00fc g\u00fcvenli bir kurulumun par\u00e7as\u0131d\u0131r.<\/p>\n<\/div>\n<h2 id=\"quic-bir-siteyi-ne-zaman-gercekten-hizlandirir\">QUIC bir siteyi ne zaman ger\u00e7ekten h\u0131zland\u0131r\u0131r?<\/h2>\n<p>QUIC&#8217;in en belirgin faydalar\u0131 y\u00fcksek gecikmeli veya paket kay\u0131pl\u0131 ba\u011flant\u0131larda ve istemcilerin Wi-Fi ile mobil veri aras\u0131nda s\u0131k ge\u00e7i\u015f yapt\u0131\u011f\u0131 a\u011flarda g\u00f6r\u00fclebilir. Ayn\u0131 anda \u00e7ok say\u0131da k\u00fc\u00e7\u00fck kaynak isteyen sayfalar, ba\u011f\u0131ms\u0131z ak\u0131\u015flardan ve daha az el s\u0131k\u0131\u015fma gecikmesinden yararlanabilir.<\/p>\n<p>Yak\u0131ndaki, paket kayb\u0131 olmayan bir sunucuda iyi \u00f6nbelle\u011fe al\u0131nm\u0131\u015f bir sayfada fark k\u00fc\u00e7\u00fck kalabilir. CDN sayfay\u0131 sunuyorsa, HTML tek ve k\u00fc\u00e7\u00fck bir dosyaysa veya backend yan\u0131t\u0131 \u00fcretmek i\u00e7in 800 milisaniye harc\u0131yorsa ta\u015f\u0131ma katman\u0131ndaki birka\u00e7 milisaniye toplam s\u00fcreyi belirlemez.<\/p>\n<p>Yaln\u0131zca TTFB&#8217;yi \u00f6l\u00e7meyin. \u0130lk ba\u011flant\u0131lar\u0131, yeniden kullan\u0131lan ba\u011flant\u0131lar\u0131, \u00f6nbelle\u011fe al\u0131nm\u0131\u015f kaynaklar\u0131, paket kayb\u0131n\u0131 ve p95 ile p99 gecikmeyi kar\u015f\u0131la\u015ft\u0131r\u0131n. <em><a href=\"https:\/\/www.vps.tc\/blog\/en\/vps-bandwidth-explained-how-much-do-you-need\/\">VPS Bandwidth Explained: How Much Do You Need?<\/a><\/em> kapasite planlamas\u0131 i\u00e7in yararl\u0131; fakat bant geni\u015fli\u011fi ile gecikme ayn\u0131 \u00f6l\u00e7\u00fcm de\u011fildir.<\/p>\n<table>\n<thead>\n<tr>\n<th>\u00d6l\u00e7\u00fcm<\/th>\n<th>Ne g\u00f6sterir?<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Protokol se\u00e7imi<\/td>\n<td>\u0130stemcilerin ger\u00e7ekten HTTP\/3&#8217;e ge\u00e7ip ge\u00e7medi\u011fini<\/td>\n<\/tr>\n<tr>\n<td>\u0130lk bayta kadar ge\u00e7en s\u00fcre<\/td>\n<td>Ta\u015f\u0131ma gecikmesi, uygulama s\u00fcresi ve \u00f6nbellek performans\u0131n\u0131n birle\u015fimini<\/td>\n<\/tr>\n<tr>\n<td>p95\/p99 gecikme<\/td>\n<td>Yava\u015f istemci grubunun ortalamada gizlenip gizlenmedi\u011fini<\/td>\n<\/tr>\n<tr>\n<td>UDP paket kayb\u0131<\/td>\n<td>Kay\u0131p paketler kurtar\u0131l\u0131rken QUIC&#8217;in nas\u0131l davrand\u0131\u011f\u0131n\u0131<\/td>\n<\/tr>\n<tr>\n<td>Hata ve geri d\u00f6n\u00fc\u015f oran\u0131<\/td>\n<td>UDP \u00e7al\u0131\u015fmad\u0131\u011f\u0131nda TCP&#8217;ye d\u00f6n\u00fc\u015f\u00fcn ba\u015far\u0131l\u0131 olup olmad\u0131\u011f\u0131n\u0131<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>CDN varsa HTTP\/3 \u00e7o\u011fu zaman origin sunucuda de\u011fil edge noktas\u0131nda sonland\u0131r\u0131l\u0131r. Ziyaret\u00e7i ile edge aras\u0131ndaki b\u00f6l\u00fcm QUIC kullan\u0131rken edge ile origin aras\u0131ndaki b\u00f6l\u00fcm TCP olabilir. Hangi \u00f6l\u00e7\u00fcm\u00fcn yolun hangi k\u0131sm\u0131n\u0131 kapsad\u0131\u011f\u0131n\u0131 kaydedin.<\/p>\n<p><strong>Ne yapmal\u0131?<\/strong> Ayn\u0131 URL ve i\u00e7erik i\u00e7in, benzer istemci ko\u015fullar\u0131nda HTTP\/2 ile HTTP\/3 p95 gecikmesini ayr\u0131 ayr\u0131 kar\u015f\u0131la\u015ft\u0131r\u0131n.<\/p>\n<div class=\"aiw-callout aiw-callout-example\">\n<p class=\"aiw-callout-label\">Example<\/p>\n<p>Bir ziyaret\u00e7i CDN edge noktas\u0131na HTTP\/3 ile ba\u011flan\u0131rken edge, origin sunucunuza HTTP\/2 veya HTTP\/1.1 ile ba\u011flanabilir. \u0130yile\u015fmeyi origin sunucusuna ba\u011flamadan \u00f6nce her b\u00f6l\u00fcm\u00fc ayr\u0131 \u00f6l\u00e7\u00fcn.<\/p>\n<\/div>\n<h2 id=\"quic-sinirlamalari-ve-guvenlik-noktalari\">QUIC s\u0131n\u0131rlamalar\u0131 ve g\u00fcvenlik noktalar\u0131<\/h2>\n<p>QUIC her a\u011fda kusursuz \u00e7al\u0131\u015fmaz. Eski baz\u0131 g\u00fcvenlik duvarlar\u0131 ve izleme sistemleri TCP&#8217;yi ayr\u0131nt\u0131l\u0131 bi\u00e7imde tan\u0131rken UDP&#8217;yi k\u0131s\u0131tlayabilir veya tamamen engelleyebilir. B\u00f6yle bir durumda HTTP\/3 ba\u011flanamaz; TCP geri d\u00f6n\u00fc\u015f\u00fc de yoksa kullan\u0131c\u0131 hata g\u00f6r\u00fcr.<\/p>\n<p>\u0130zleme sisteminin de de\u011fi\u015fmesi gerekir. TCP ba\u011flant\u0131lar\u0131 etraf\u0131nda haz\u0131rlanm\u0131\u015f dashboard&#8217;lar QUIC ak\u0131\u015f durumunu do\u011fru g\u00f6stermeyebilir. Sunucudan veya proxy&#8217;den QUIC metriklerini, UDP paket kayb\u0131n\u0131, el s\u0131k\u0131\u015fma hatalar\u0131n\u0131, ba\u011flant\u0131 ta\u015f\u0131nmalar\u0131n\u0131 ve geri d\u00f6n\u00fc\u015f oranlar\u0131n\u0131 toplay\u0131n.<\/p>\n<p>0-RTT, yeniden kurulan ba\u011flant\u0131larda gecikmeyi azaltabilir. Fakat RFC 9001&#8217;de a\u00e7\u0131klanan TLS 1.3 modeli i\u00e7inde 0-RTT verisi yeniden oynatma riskine a\u00e7\u0131kt\u0131r. Para transferi, sipari\u015f olu\u015fturma, parola de\u011fi\u015ftirme veya ba\u015fka yan etki \u00fcreten i\u015flemleri 0-RTT verisi olarak ko\u015fulsuz kabul etmeyin. \u0130dempotent GET istekleri daha uygun adaylard\u0131r.<\/p>\n<p>QUIC trafi\u011fi \u015fifreli oldu\u011fu i\u00e7in a\u011f y\u00f6neticileri i\u00e7eri\u011fi do\u011frudan inceleyemez. Bu gizlilik i\u00e7in olumludur; ancak sorun giderme ve politika uygulama bi\u00e7imini de\u011fi\u015ftirir. TLS anahtar g\u00fcnl\u00fc\u011f\u00fc, u\u00e7 nokta metrikleri ve kontroll\u00fc paket analizi kurumun g\u00fcvenlik politikas\u0131na g\u00f6re tasarlanmal\u0131d\u0131r.<\/p>\n<p>HTTP\/3&#8217;\u00fc a\u00e7mak k\u00f6t\u00fc yap\u0131land\u0131r\u0131lm\u0131\u015f bir uygulamay\u0131 d\u00fczeltmez. Yava\u015f bir veritaban\u0131 sorgusu, s\u0131k\u0131\u015ft\u0131r\u0131lmam\u0131\u015f bir g\u00f6rsel veya hatal\u0131 cache ba\u015fl\u0131\u011f\u0131 yine yava\u015ft\u0131r. Ta\u015f\u0131ma katman\u0131n\u0131 su\u00e7lamadan \u00f6nce uygulama ve proxy hatalar\u0131n\u0131, \u00f6rne\u011fin <em><a href=\"https:\/\/www.vps.tc\/blog\/en\/how-to-fix-502-bad-gateway-error\/\">How to Fix a 502 Bad Gateway Error<\/a><\/em> yaz\u0131s\u0131nda anlat\u0131lan 502 durumlar\u0131n\u0131, ay\u0131r\u0131n.<\/p>\n<p>\u015eifreli olmas\u0131 izleme ihtiyac\u0131n\u0131 ortadan kald\u0131rmaz. Sadece izlenecek sinyalleri de\u011fi\u015ftirir.<\/p>\n<h2 id=\"uygulanabilir-bir-quic-gecis-plani\">Uygulanabilir bir QUIC ge\u00e7i\u015f plan\u0131<\/h2>\n<p>\u00dcretimde UDP 443&#8217;\u00fc a\u00e7\u0131p beklemek bir ge\u00e7i\u015f plan\u0131 de\u011fildir. \u00d6nce ger\u00e7ekten \u00e7al\u0131\u015ft\u0131rd\u0131\u011f\u0131n\u0131z sunucu s\u00fcr\u00fcm\u00fcnde HTTP\/3 deste\u011fini, TLS sertifikas\u0131n\u0131 ve \u00e7ekirdek g\u00fcvenlik duvar\u0131 kurallar\u0131n\u0131 do\u011frulay\u0131n. \u00d6n\u00fcn\u00fczde load balancer veya CDN varsa onun QUIC deste\u011fini ayr\u0131ca kontrol edin.<\/p>\n<ol>\n<li>Alan ad\u0131n\u0131n A ve AAAA kay\u0131tlar\u0131n\u0131 do\u011frulay\u0131n.<\/li>\n<li>Geri d\u00f6n\u00fc\u015f i\u00e7in TCP 443&#8217;\u00fc a\u00e7\u0131k tutun.<\/li>\n<li>Security group ve nftables \u00fczerinde UDP 443&#8217;\u00fc kontroll\u00fc bir de\u011fi\u015fiklikle a\u00e7\u0131n.<\/li>\n<li>HTTP\/3 destekli sunucuyu veya reverse proxy&#8217;yi ana \u00fcretim yolunun d\u0131\u015f\u0131nda test edin.<\/li>\n<li>curl ve taray\u0131c\u0131 geli\u015ftirici ara\u00e7lar\u0131yla anla\u015f\u0131lm\u0131\u015f protokol\u00fc do\u011frulay\u0131n.<\/li>\n<li>HTTP\/2&#8217;de kalan istemcilerden gelen hatalar\u0131 izleyin.<\/li>\n<li>Hata, gecikme, CPU kullan\u0131m\u0131 ve UDP paket kayb\u0131n\u0131 kar\u015f\u0131la\u015ft\u0131r\u0131n.<\/li>\n<\/ol>\n<p>HTTP\/3&#8217;\u00fcn bir hostname \u00fczerinde \u00e7al\u0131\u015f\u0131p di\u011ferinde \u00e7al\u0131\u015fmamas\u0131 normaldir; her edge, proxy ve DNS katman\u0131n\u0131n ayar\u0131 farkl\u0131 olabilir. <em><a href=\"https:\/\/www.vps.tc\/blog\/en\/how-to-fix-dns-probe-finished-nxdomain-error\/\">How to Fix DNS_PROBE_FINISHED_NXDOMAIN Error<\/a><\/em> yaz\u0131s\u0131ndaki temel yakla\u015f\u0131m DNS kontrollerinde yard\u0131mc\u0131 olur; fakat QUIC incelemesi UDP yolunu da test etmelidir.<\/p>\n<p>Geri d\u00f6n\u00fc\u015f\u00fcn\u00fcz basit olmal\u0131: UDP 443&#8217;\u00fc kapatmak veya HTTP\/3 duyurusunu kald\u0131rmak TCP 443 \u00fczerinden kullan\u0131c\u0131 sunumunu b\u0131rakmamal\u0131. De\u011fi\u015fiklikten \u00f6nce HTTP\/2 \u00f6l\u00e7\u00fcmlerini saklay\u0131n; aksi halde h\u0131z art\u0131\u015f\u0131 iddian\u0131z\u0131n g\u00fcvenilir bir ba\u015flang\u0131\u00e7 noktas\u0131 olmaz.<\/p>\n<p>Ama\u00e7 her ziyaret\u00e7iyi QUIC&#8217;e zorlamak de\u011fil. Uyumlu istemcilere HTTP\/3, di\u011ferlerine HTTP\/2 veya HTTP\/1.1 sunmak daha toleransl\u0131 bir servis olu\u015fturur.<\/p>\n<p><strong>Ne yapmal\u0131?<\/strong> HTTP\/3&#8217;\u00fc \u00f6nce \u00f6l\u00e7\u00fclebilir bir trafik dilimine a\u00e7\u0131n; ayn\u0131 g\u00fcn i\u00e7inde hem geri d\u00f6n\u00fc\u015f\u00fc hem de rollback&#8217;i test edin.<\/p>\n<div class=\"aiw-callout aiw-callout-field\">\n<p class=\"aiw-callout-label\">From the field<\/p>\n<p>Laboratuvar\u0131mda ta\u015f\u0131ma kontrollerini ayr\u0131 tutuyorum: DNS \u00e7\u00f6z\u00fcmlemesi, dinleyen soket, g\u00fcvenlik duvar\u0131 kurallar\u0131 ve istemci yetene\u011fi birbirinden ba\u011f\u0131ms\u0131z kontroller. Daha \u00f6nce hizmetin dinliyor olmas\u0131n\u0131 b\u00fct\u00fcn yolun \u00e7al\u0131\u015ft\u0131\u011f\u0131na kan\u0131p gereksiz zaman kaybettim.<\/p>\n<\/div>\n<h2 id=\"http-3u-acmadan-once-bunlari-kontrol-edin\">HTTP\/3&#039;\u00fc A\u00e7madan \u00d6nce Bunlar\u0131 Kontrol Edin<\/h2>\n<ul class=\"aiw-checklist\">\n<li>Hostname i\u00e7in A ve AAAA kay\u0131tlar\u0131n\u0131 do\u011frulay\u0131n.<\/li>\n<li>HTTP\/2 ve HTTP\/1.1 geri d\u00f6n\u00fc\u015f\u00fc i\u00e7in TCP 443&#039;\u00fc a\u00e7\u0131k tutun.<\/li>\n<li>Sa\u011flay\u0131c\u0131 security group&#039;unda ve host g\u00fcvenlik duvar\u0131nda UDP 443&#039;e izin verin.<\/li>\n<li>Proxy, CDN veya web sunucunuzun HTTP\/3 destekledi\u011fini do\u011frulay\u0131n.<\/li>\n<li>Sunucuyu incelemeden \u00f6nce curl -V ile istemci deste\u011fini kontrol edin.<\/li>\n<li>Taray\u0131c\u0131 geli\u015ftirici ara\u00e7lar\u0131nda anla\u015f\u0131lm\u0131\u015f protokol\u00fc kontrol edin.<\/li>\n<li>Gecikme, hatalar, CPU kullan\u0131m\u0131, paket kayb\u0131 ve geri d\u00f6n\u00fc\u015f oranlar\u0131n\u0131 kar\u015f\u0131la\u015ft\u0131r\u0131n.<\/li>\n<\/ul>\n<div class=\"aiw-cta\">\n<p>Sunucunuz ve edge a\u011f\u0131n\u0131z destekliyorsa HTTP\/3&#039;\u00fc HTTP\/2&#039;nin yan\u0131na ekleyin, onun yerine koymay\u0131n. Ger\u00e7ek istemci yolunu \u00f6l\u00e7\u00fcn, geri d\u00f6n\u00fc\u015f\u00fc \u00e7al\u0131\u015f\u0131r durumda tutun; QUIC&#039;in \u00fcretim yap\u0131land\u0131rman\u0131za uygun olup olmad\u0131\u011f\u0131na protokol ad\u0131 de\u011fil, sonu\u00e7lar karar versin.<\/p>\n<p class=\"aiw-cta-action\"><a href=\"https:\/\/www.vps.tc\/en\/vps\">Explore VPS plans<\/a><\/p>\n<\/div>\n<h2 id=\"frequently-asked-questions\">Frequently Asked Questions<\/h2>\n<div class=\"aiw-faq\">\n<details class=\"aiw-faq-item\" open>\n<summary>QUIC basit\u00e7e nedir?<\/summary>\n<p>QUIC, UDP kullanan fakat uygulamalar\u0131n ihtiya\u00e7 duydu\u011fu g\u00fcvenilirlik, paket kayb\u0131 kurtarma, t\u0131kan\u0131kl\u0131k kontrol\u00fc ve s\u0131ralama i\u015flerini kendi katman\u0131nda sa\u011flayan modern bir ta\u015f\u0131ma protokol\u00fcd\u00fcr. TLS 1.3&#039;\u00fc ba\u011flant\u0131 kurulumu ile birlikte kullan\u0131r. HTTP\/3, HTTP istek ve yan\u0131tlar\u0131n\u0131 QUIC \u00fczerinden ta\u015f\u0131r. QUIC ta\u015f\u0131ma katman\u0131d\u0131r; HTTP\/3 ise onun \u00fczerindeki HTTP katman\u0131d\u0131r.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>QUIC TCP&#039;den daha h\u0131zl\u0131 m\u0131?<\/summary>\n<p>QUIC \u00f6zellikle y\u00fcksek gecikme, paket kayb\u0131 veya s\u0131k a\u011f de\u011fi\u015fikli\u011fi bulunan ba\u011flant\u0131larda daha h\u0131zl\u0131 olabilir. TLS el s\u0131k\u0131\u015fmas\u0131n\u0131n yap\u0131s\u0131 ve ba\u011f\u0131ms\u0131z ak\u0131\u015flar baz\u0131 gecikmeleri azalt\u0131r. Her sayfada otomatik olarak daha h\u0131zl\u0131 de\u011fildir. Yak\u0131n sunucu, iyi \u00f6nbellekleme, yava\u015f backend veya k\u00fc\u00e7\u00fck HTML yan\u0131t\u0131 HTTP\/2 ile HTTP\/3 aras\u0131ndaki fark\u0131 g\u00f6r\u00fcnmez k\u0131labilir.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>QUIC TCP mi, UDP mi kullan\u0131r?<\/summary>\n<p>QUIC UDP kullan\u0131r ve HTTP\/3 i\u00e7in genellikle UDP 443 \u00fczerinde \u00e7al\u0131\u015f\u0131r. UDP kendi ba\u015f\u0131na g\u00fcvenilir teslimat veya s\u0131ralama sa\u011flamad\u0131\u011f\u0131 i\u00e7in bu i\u015flevleri QUIC \u00fcstlenir. Bu tasar\u0131m QUIC&#039;in yaln\u0131zca \u00e7ekirdek TCP y\u0131\u011f\u0131n\u0131na ba\u011fl\u0131 kalmadan kullan\u0131c\u0131 alan\u0131nda \u00e7al\u0131\u015fmas\u0131na da imk\u00e2n verir. UDP kullanamayan istemciler i\u00e7in TCP 443 ve HTTP\/2 veya HTTP\/1.1 geri d\u00f6n\u00fc\u015f\u00fc a\u00e7\u0131k kalmal\u0131d\u0131r.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>HTTP\/3 ile QUIC ayn\u0131 \u015fey mi?<\/summary>\n<p>Hay\u0131r. QUIC \u015fifreli ta\u015f\u0131ma protokol\u00fcd\u00fcr; HTTP\/3 ise QUIC \u00fczerinde \u00e7al\u0131\u015fmak \u00fczere tasarlanm\u0131\u015f HTTP s\u00fcr\u00fcm\u00fcd\u00fcr. HTTP\/3; metotlar, ba\u015fl\u0131klar, durum kodlar\u0131 ve istek g\u00f6vdeleri gibi tan\u0131d\u0131k HTTP kavramlar\u0131n\u0131 korur. De\u011fi\u015fen b\u00f6l\u00fcm, ba\u011flant\u0131 kurulumu ve ak\u0131\u015f y\u00f6netimi dahil olmak \u00fczere alttaki ta\u015f\u0131mad\u0131r. Bu ikisini kar\u0131\u015ft\u0131rmak g\u00fcvenlik duvar\u0131, proxy ve performans incelemesini yanl\u0131\u015f y\u00f6ne g\u00f6t\u00fcrebilir.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>QUIC hangi portu kullan\u0131r?<\/summary>\n<p>HTTP\/3 sunucu taraf\u0131nda \u00e7o\u011funlukla UDP 443 kullan\u0131r. Sa\u011flay\u0131c\u0131 security group&#039;unu, host g\u00fcvenlik duvar\u0131n\u0131, reverse proxy&#039;yi, CDN&#039;i ve istemci ile sunucu aras\u0131ndaki a\u011f cihazlar\u0131n\u0131 da kontrol etmeniz gerekir. HTTP\/2 ve HTTP\/1.1 geri d\u00f6n\u00fc\u015f\u00fc i\u00e7in TCP 443 normalde a\u00e7\u0131k kalmal\u0131d\u0131r. Sunucunun UDP 443 \u00fczerinde dinlemesi, \u00fcst taraftaki g\u00fcvenlik duvar\u0131n\u0131n paketlere izin verdi\u011fi anlam\u0131na gelmez.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>QUIC ba\u011flant\u0131lar\u0131 Wi-Fi&#039;dan mobile ge\u00e7i\u015fte devam edebilir mi?<\/summary>\n<p>Devam edebilir; \u00e7\u00fcnk\u00fc QUIC yaln\u0131zca istemcinin IP adresine ve portuna dayanmak yerine Connection ID de\u011ferlerini kullan\u0131r. Bu, TCP&#039;nin \u00e7o\u011fu zaman yeni ba\u011flant\u0131 gerektirece\u011fi durumlarda ba\u011flant\u0131n\u0131n ta\u015f\u0131nmas\u0131na yard\u0131mc\u0131 olabilir. Garanti yoktur: NAT e\u015flemeleri, g\u00fcvenlik duvarlar\u0131, sunucu politikalar\u0131 ve yeni a\u011f yolunun kalitesi sonucu belirler. Ba\u011flant\u0131 ta\u015f\u0131nmas\u0131n\u0131 destekleyen bir protokol her a\u011f ge\u00e7i\u015fini g\u00f6r\u00fcnmez h\u00e2le getirmez.<\/p>\n<\/details>\n<\/div>\n<h2 id=\"sources\">Sources<\/h2>\n<ul class=\"aiw-sources\">\n<li><a href=\"https:\/\/www.rfc-editor.org\/rfc\/rfc9000\" target=\"_blank\" rel=\"noopener\">RFC 9000 &#8211; QUIC: A UDP-Based Multiplexed and Secure Transport<\/a> \u2014 rfc-editor.org<\/li>\n<li><a href=\"https:\/\/www.rfc-editor.org\/rfc\/rfc9001\" target=\"_blank\" rel=\"noopener\">RFC 9001 &#8211; Using TLS to Secure QUIC<\/a> \u2014 rfc-editor.org<\/li>\n<li><a href=\"https:\/\/www.rfc-editor.org\/rfc\/rfc9114\" target=\"_blank\" rel=\"noopener\">RFC 9114 &#8211; HTTP\/3<\/a> \u2014 rfc-editor.org<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>QUIC, HTTP\/3&#8217;\u00fcn arkas\u0131ndaki ta\u015f\u0131ma protokol\u00fcd\u00fcr. Ba\u011f\u0131ms\u0131z ak\u0131\u015flar\u0131, TLS 1.3 entegrasyonu, ba\u011flant\u0131 ta\u015f\u0131nmas\u0131 ve UDP kullan\u0131m\u0131 VPS performans\u0131n\u0131 nas\u0131l etkiler, \u00f6l\u00e7erek inceleyin.<\/p>\n","protected":false},"author":2,"featured_media":792,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4],"tags":[],"class_list":["post-794","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-technology"],"lang":"en","translations":{"en":794,"tr":793},"pll_sync_post":[],"_links":{"self":[{"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/posts\/794","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/comments?post=794"}],"version-history":[{"count":1,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/posts\/794\/revisions"}],"predecessor-version":[{"id":796,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/posts\/794\/revisions\/796"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/media\/792"}],"wp:attachment":[{"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/media?parent=794"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/categories?post=794"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/tags?post=794"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}