{"id":793,"date":"2026-09-17T12:28:50","date_gmt":"2026-09-17T12:28:50","guid":{"rendered":"https:\/\/www.vps.tc\/blog\/?p=793"},"modified":"2026-09-17T10:20:04","modified_gmt":"2026-09-17T10:20:04","slug":"quic-nedir-http3-ve-tcp-farklari","status":"publish","type":"post","link":"https:\/\/www.vps.tc\/blog\/tr\/quic-nedir-http3-ve-tcp-farklari\/","title":{"rendered":"QUIC Nedir? Daha H\u0131zl\u0131 \u0130nternet Protokol\u00fc"},"content":{"rendered":"<div class=\"aiw-summary\" id=\"aiw-ozet\">\n<p class=\"aiw-summary-title\">H\u0131zl\u0131 \u00d6zet &#8211; QUIC ve HTTP\/3<\/p>\n<p>QUIC, UDP \u00fczerinde \u00e7al\u0131\u015fan ve TLS 1.3&#039;\u00fc ba\u011flant\u0131 kurulumu ile b\u00fct\u00fcnle\u015ftiren g\u00fcvenli ta\u015f\u0131ma protokol\u00fcd\u00fcr. HTTP\/3, HTTP isteklerini QUIC ak\u0131\u015flar\u0131 \u00fczerinden ta\u015f\u0131r.<\/p>\n<ul>\n<li><strong>Temel port<\/strong> \u2014 Web sunucular\u0131nda QUIC i\u00e7in genellikle UDP 443 kullan\u0131l\u0131r; TCP 443 geri d\u00f6n\u00fc\u015f i\u00e7in a\u00e7\u0131k kalmal\u0131d\u0131r.<\/li>\n<li><strong>HTTP ili\u015fkisi<\/strong> \u2014 QUIC ta\u015f\u0131ma katman\u0131d\u0131r, HTTP\/3 ise onun \u00fczerinde \u00e7al\u0131\u015fan HTTP s\u00fcr\u00fcm\u00fcd\u00fcr.<\/li>\n<li><strong>H\u0131z kayna\u011f\u0131<\/strong> \u2014 Daha az el s\u0131k\u0131\u015fma, ba\u011f\u0131ms\u0131z ak\u0131\u015flar ve ba\u011flant\u0131 g\u00f6\u00e7\u00fc baz\u0131 a\u011flarda gecikmeyi azaltabilir.<\/li>\n<li><strong>G\u00fcvenlik<\/strong> \u2014 QUIC, TLS 1.3 ile b\u00fct\u00fcnle\u015fik \u00e7al\u0131\u015f\u0131r; 0-RTT verileri yeniden oynatma riskine kar\u015f\u0131 dikkat ister.<\/li>\n<li><strong>Fallback<\/strong> \u2014 UDP engellendi\u011finde uyumlu bir yap\u0131land\u0131rma istemciyi HTTP\/2 veya HTTP\/1.1&#039;e d\u00f6nd\u00fcrmelidir.<\/li>\n<li><strong>\u00d6l\u00e7\u00fcm<\/strong> \u2014 Ba\u015far\u0131y\u0131 yaln\u0131zca TTFB ile de\u011fil, protokol se\u00e7imi, p95 gecikme, paket kayb\u0131 ve hata oran\u0131yla de\u011ferlendirin.<\/li>\n<\/ul>\n<\/div>\n<p class=\"aiw-lead\">QUIC, UDP \u00fczerinde \u00e7al\u0131\u015fan; g\u00fcvenilir ta\u015f\u0131ma, TLS 1.3 \u015fifreleme, \u00e7oklu ak\u0131\u015f ve ba\u011flant\u0131 g\u00f6\u00e7\u00fcn\u00fc tek protokolde birle\u015ftiren ta\u015f\u0131ma katman\u0131d\u0131r. HTTP\/3 bu katman\u0131 kullan\u0131r. QUIC her siteyi otomatik h\u0131zland\u0131rmaz; etkisi \u00f6zellikle paket kayb\u0131, y\u00fcksek gecikme ve mobil a\u011f de\u011fi\u015fimlerinde \u00f6l\u00e7\u00fcl\u00fcr.<\/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>\u0130\u00e7indekiler<\/strong><span class=\"aiw-toc-meta\"> \u00b7 12 dk okuma<\/span><\/p>\n<ol style=\"margin:10px 0 0;padding-left:22px\">\n<li><a href=\"#quic-nedir-ve-hangi-sorunu-cozer\">QUIC nedir ve 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-ile-tcp-ve-http-2-arasindaki-fark-nedir\">QUIC ile TCP ve HTTP\/2 aras\u0131ndaki fark nedir?<\/a><\/li>\n<li><a href=\"#http-3-ile-quic-iliskisi-nedir\">HTTP\/3 ile QUIC ili\u015fkisi nedir?<\/a><\/li>\n<li><a href=\"#sunucuda-http-3-ve-quic-nasil-test-edilir\">Sunucuda HTTP\/3 ve QUIC nas\u0131l test edilir?<\/a><\/li>\n<li><a href=\"#quic-kullanirken-hangi-portlar-ve-firewall-kurallari-gerekir\">QUIC kullan\u0131rken hangi portlar ve firewall kurallar\u0131 gerekir?<\/a><\/li>\n<li><a href=\"#quicin-hiz-avantaji-her-sitede-gorulur-mu\">QUIC&#039;in h\u0131z avantaj\u0131 her sitede g\u00f6r\u00fcl\u00fcr m\u00fc?<\/a><\/li>\n<li><a href=\"#quicin-dezavantajlari-ve-guvenlik-sinirlari-nelerdir\">QUIC&#039;in dezavantajlar\u0131 ve g\u00fcvenlik s\u0131n\u0131rlar\u0131 nelerdir?<\/a><\/li>\n<li><a href=\"#quic-etkinlestirmeden-once-nasil-bir-gecis-plani-izlenir\">QUIC etkinle\u015ftirmeden \u00f6nce nas\u0131l bir ge\u00e7i\u015f plan\u0131 izlenir?<\/a><\/li>\n<li><a href=\"#quic-kurulumundan-once-sunlari-kontrol-edin\">QUIC Kurulumundan \u00d6nce \u015eunlar\u0131 Kontrol Edin<\/a><\/li>\n<li><a href=\"#sik-sorulan-sorular\">S\u0131k Sorulan Sorular<\/a><\/li>\n<li><a href=\"#kaynaklar\">Kaynaklar<\/a><\/li>\n<\/ol>\n<\/div>\n<h2 id=\"quic-nedir-ve-hangi-sorunu-cozer\">QUIC nedir ve hangi sorunu \u00e7\u00f6zer?<\/h2>\n<p>QUIC, uygulama katman\u0131ndaki HTTP trafi\u011fini UDP \u00fczerinde ta\u015f\u0131yan, ba\u011flant\u0131 kurulumu ile TLS 1.3 \u015fifrelemesini birlikte tasarlayan modern bir ta\u015f\u0131ma protokol\u00fcd\u00fcr. IETF&#8217;nin RFC 9000 standard\u0131na g\u00f6re QUIC; ak\u0131\u015f \u00e7oklama, ba\u011flant\u0131 kimlikleri, kay\u0131p paket kurtarma ve ba\u011flant\u0131 g\u00f6\u00e7\u00fc gibi \u00f6zellikler sunar. HTTP\/3 ise HTTP semanti\u011fini QUIC ak\u0131\u015flar\u0131 \u00fczerinde \u00e7al\u0131\u015ft\u0131r\u0131r.<\/p>\n<p>Ayr\u0131m nettir: QUIC ta\u015f\u0131ma katman\u0131d\u0131r; HTTP\/3, bu ta\u015f\u0131ma katman\u0131n\u0131 kullanan HTTP s\u00fcr\u00fcm\u00fcd\u00fcr. Bir web sunucusunda HTTP\/3 etkinle\u015ftirildi\u011finde genellikle UDP 443 \u00fczerinden QUIC, TCP 443 \u00fczerinden de HTTP\/2 veya HTTP\/1.1 birlikte sunulur.<\/p>\n<p>TCP y\u0131llard\u0131r g\u00fcvenilir bir temel sa\u011fl\u0131yor. Ancak TCP ba\u011flant\u0131s\u0131ndaki paket kayb\u0131, ayn\u0131 ba\u011flant\u0131 i\u00e7indeki b\u00fct\u00fcn veri ak\u0131\u015flar\u0131n\u0131 etkileyebilir. QUIC verileri ba\u011f\u0131ms\u0131z ak\u0131\u015flara ay\u0131r\u0131r. Bir ak\u0131\u015fta paket kayboldu\u011funda di\u011fer ak\u0131\u015flar\u0131n verisi, kay\u0131p paket yeniden g\u00f6nderilene kadar zorunlu olarak beklemek zorunda kalmaz.<\/p>\n<p><strong>Ne yap\u0131lmal\u0131<\/strong> &#8211; QUIC&#8217;i HTTP\/3 ile birlikte de\u011ferlendirin; protokol\u00fcn ta\u015f\u0131ma katman\u0131, HTTP\/3&#8217;\u00fcn ise uygulama katman\u0131 oldu\u011funu yap\u0131land\u0131rma s\u0131ras\u0131nda ay\u0131r\u0131n.<\/p>\n<h2 id=\"quic-nasil-calisir\">QUIC nas\u0131l \u00e7al\u0131\u015f\u0131r?<\/h2>\n<p>Bir QUIC ba\u011flant\u0131s\u0131 UDP kulland\u0131\u011f\u0131 i\u00e7in basit g\u00f6r\u00fcnebilir. Ger\u00e7ekte g\u00fcvenilirlik, s\u0131ra kontrol\u00fc, ak\u0131\u015f y\u00f6netimi, t\u0131kan\u0131kl\u0131k kontrol\u00fc ve \u015fifreleme gibi TCP&#8217;nin y\u0131llar i\u00e7inde kazand\u0131\u011f\u0131 i\u015flevlerin b\u00fcy\u00fck b\u00f6l\u00fcm\u00fcn\u00fc kullan\u0131c\u0131 alan\u0131nda yeniden kurar.<\/p>\n<h3>UDP \u00fczerinde g\u00fcvenilir ta\u015f\u0131ma<\/h3>\n<p>UDP, paketlerin teslim edilece\u011fini veya do\u011fru s\u0131rada ula\u015faca\u011f\u0131n\u0131 garanti etmez. QUIC bu eksikli\u011fi paket numaralar\u0131, onay paketleri ve kay\u0131p kurtarma algoritmalar\u0131yla giderir. Bu y\u00fczden &#8220;UDP oldu\u011fu i\u00e7in g\u00fcvenilir de\u011fil&#8221; yorumu eksiktir. G\u00fcvenilirlik UDP&#8217;den de\u011fil, QUIC katman\u0131ndan gelir.<\/p>\n<p>QUIC paketleri do\u011frudan i\u015fletim sistemi \u00e7ekirde\u011findeki TCP y\u0131\u011f\u0131n\u0131na ba\u011fl\u0131 de\u011fildir. Uygulama veya k\u00fct\u00fcphane, protokol davran\u0131\u015f\u0131n\u0131 daha h\u0131zl\u0131 g\u00fcncelleyebilir. Yeni bir TCP \u00f6zelli\u011fi i\u00e7in i\u015fletim sistemi ve a\u011f cihaz\u0131 deste\u011fi beklemek gerekebilir; QUIC&#8217;in kullan\u0131c\u0131 alan\u0131nda uygulanmas\u0131 bu s\u00fcreci k\u0131saltabilir.<\/p>\n<h3>Ba\u011flant\u0131 kimli\u011fi ve a\u011f de\u011fi\u015fikli\u011fi<\/h3>\n<p>TCP ba\u011flant\u0131lar\u0131 \u00e7o\u011funlukla istemci IP&#8217;si, istemci portu, sunucu IP&#8217;si ve sunucu portundan olu\u015fan d\u00f6rt par\u00e7al\u0131 tan\u0131mlay\u0131c\u0131ya ba\u011fl\u0131d\u0131r. \u0130stemci Wi-Fi&#8217;dan mobil a\u011fa ge\u00e7ti\u011finde bu bilgiler de\u011fi\u015fir ve TCP ba\u011flant\u0131s\u0131 kopabilir.<\/p>\n<p>QUIC ba\u011flant\u0131lar\u0131 ise Connection ID ad\u0131 verilen kimliklerle takip edilebilir. \u0130stemci ayn\u0131 ba\u011flant\u0131y\u0131 koruyarak a\u011f de\u011fi\u015ftirebilir. Bu \u00f6zellik, \u00f6zellikle mobil cihazlarda veya s\u0131k Wi-Fi ge\u00e7i\u015fi ya\u015fanan ortamlarda yeniden ba\u011flant\u0131 maliyetini azaltabilir. Her a\u011f de\u011fi\u015fiminde ba\u011flant\u0131n\u0131n kesinlikle korunaca\u011f\u0131 anlam\u0131na gelmez; NAT, g\u00fcvenlik duvar\u0131 ve sunucu politikalar\u0131 yine belirleyicidir.<\/p>\n<h3>Ak\u0131\u015flar ve head-of-line blocking<\/h3>\n<p>HTTP\/2, tek TCP ba\u011flant\u0131s\u0131 \u00fczerinde birden fazla istek ve yan\u0131t\u0131 \u00e7oklayabilir. Bu, ba\u011flant\u0131 say\u0131s\u0131n\u0131 azalt\u0131r; fakat TCP seviyesinde kaybolan bir paket, o paketten sonraki b\u00fct\u00fcn verilerin teslimini etkileyebilir. Buna head-of-line blocking denir.<\/p>\n<p>QUIC \u00e7oklamay\u0131 ta\u015f\u0131ma katman\u0131n\u0131n i\u00e7ine al\u0131r. Bir HTTP\/3 ba\u011flant\u0131s\u0131ndaki her istek kendi QUIC ak\u0131\u015f\u0131nda ta\u015f\u0131nabilir. Bir g\u00f6rselin ak\u0131\u015f\u0131 paket kayb\u0131 nedeniyle beklerken CSS veya ba\u015fka bir iste\u011fin ak\u0131\u015f\u0131 ilerleyebilir. Kay\u0131p paket yine yeniden g\u00f6nderilmelidir; fakat bekleme alan\u0131 daha s\u0131n\u0131rl\u0131 kal\u0131r.<\/p>\n<h2 id=\"quic-ile-tcp-ve-http-2-arasindaki-fark-nedir\">QUIC ile TCP ve HTTP\/2 aras\u0131ndaki fark nedir?<\/h2>\n<p>Kar\u015f\u0131la\u015ft\u0131rmay\u0131 yaln\u0131zca &#8220;UDP daha h\u0131zl\u0131d\u0131r&#8221; c\u00fcmlesine indirmek do\u011fru de\u011fildir. QUIC&#8217;in avantaj\u0131, UDP&#8217;nin d\u00fc\u015f\u00fck seviyeli yap\u0131s\u0131n\u0131 TLS 1.3, ak\u0131\u015f y\u00f6netimi ve ba\u011flant\u0131 kontrol\u00fcyle bir araya getirmesinden kaynaklan\u0131r.<\/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, \u00e7o\u011funlukla TCP 443<\/td>\n<td>UDP, \u00e7o\u011funlukla 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>QUIC el s\u0131k\u0131\u015fmas\u0131yla b\u00fct\u00fcnle\u015fik TLS 1.3<\/td>\n<\/tr>\n<tr>\n<td>\u00c7oklama<\/td>\n<td>HTTP\/2 ak\u0131\u015flar\u0131 TCP \u00fczerinde<\/td>\n<td>QUIC ak\u0131\u015flar\u0131 ta\u015f\u0131ma katman\u0131nda<\/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\u015fikli\u011fi<\/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 de \u00f6nerilir<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>RFC 9001, QUIC&#8217;in TLS 1.3 kullanmas\u0131n\u0131 tan\u0131mlar. Bu nedenle QUIC&#8217;i eski TLS s\u00fcr\u00fcmleriyle \u00e7al\u0131\u015ft\u0131rmak veya \u015fifrelemeyi sonradan eklenen bir katman gibi d\u00fc\u015f\u00fcnmek do\u011fru de\u011fildir. Sertifika y\u00f6netimi \u00f6nemini korur; HTTPS sertifikas\u0131, alan ad\u0131 ve istemci do\u011frulamas\u0131 HTTP\/3 taraf\u0131nda ortadan kalkmaz.<\/p>\n<p>QUIC&#8217;in ilk ba\u011flant\u0131da her zaman b\u00fcy\u00fck bir gecikme azalmas\u0131 sa\u011flamad\u0131\u011f\u0131 da hesaba kat\u0131lmal\u0131. \u0130stemci ve sunucu aras\u0131ndaki mesafe k\u0131sa, ba\u011flant\u0131 kararl\u0131 ve TLS oturumu yeniden kullan\u0131l\u0131yorsa TCP + HTTP\/2 zaten yeterince h\u0131zl\u0131 olabilir. Kazan\u00e7; el s\u0131k\u0131\u015fma say\u0131s\u0131, paket kayb\u0131, mobil a\u011f ge\u00e7i\u015fi ve paralel isteklerin yap\u0131s\u0131yla de\u011fi\u015fir.<\/p>\n<p><strong>Ne yap\u0131lmal\u0131<\/strong> &#8211; TCP 443&#8217;\u00fc kapatmadan UDP 443&#8217;\u00fc ekleyin ve ger\u00e7ek istemci davran\u0131\u015flar\u0131n\u0131 HTTP\/2 ile HTTP\/3 i\u00e7in ayr\u0131 ayr\u0131 \u00f6l\u00e7\u00fcn.<\/p>\n<h2 id=\"http-3-ile-quic-iliskisi-nedir\">HTTP\/3 ile QUIC ili\u015fkisi nedir?<\/h2>\n<p>HTTP\/3, RFC 9114 ile tan\u0131mlanan HTTP s\u00fcr\u00fcm\u00fcd\u00fcr ve QUIC \u00fczerinde \u00e7al\u0131\u015f\u0131r. HTTP y\u00f6ntemleri, durum kodlar\u0131, ba\u015fl\u0131klar ve g\u00f6vde mant\u0131\u011f\u0131 b\u00fcy\u00fck \u00f6l\u00e7\u00fcde tan\u0131d\u0131kt\u0131r; de\u011fi\u015fen b\u00f6l\u00fcm, bu HTTP mesajlar\u0131n\u0131n tel \u00fczerinde ta\u015f\u0131nma bi\u00e7imidir.<\/p>\n<p>HTTP\/2&#8217;de ba\u015fl\u0131klar HPACK ile s\u0131k\u0131\u015ft\u0131r\u0131l\u0131r. HTTP\/3 ise QPACK kullan\u0131r. QPACK, QUIC&#8217;in ba\u011f\u0131ms\u0131z ak\u0131\u015f modeline g\u00f6re tasarlanm\u0131\u015ft\u0131r; ba\u015fl\u0131k s\u0131k\u0131\u015ft\u0131rma tablosundaki g\u00fcncellemelerin di\u011fer ak\u0131\u015flar\u0131 gereksiz \u015fekilde durdurmamas\u0131 hedeflenir.<\/p>\n<p>Bir taray\u0131c\u0131, sunucunun HTTP\/3 destekledi\u011fini \u00e7o\u011funlukla Alt-Svc yan\u0131t ba\u015fl\u0131\u011f\u0131 veya HTTPS DNS kayd\u0131 \u00fczerinden \u00f6\u011frenir. \u0130lk istek TCP ile ger\u00e7ekle\u015febilir, sonraki isteklerde istemci UDP 443 \u00fczerinden QUIC ba\u011flant\u0131s\u0131n\u0131 deneyebilir. UDP ba\u015far\u0131s\u0131z olursa TCP tabanl\u0131 HTTP\/2&#8217;ye d\u00f6nmek, ge\u00e7i\u015f d\u00f6nemindeki altyap\u0131 i\u00e7in sa\u011fl\u0131kl\u0131 davran\u0131\u015ft\u0131r.<\/p>\n<p>HTTP\/3 kullan\u0131m\u0131 uygulama kodunu otomatik olarak de\u011fi\u015ftirmez. PHP, Node.js veya Python uygulaman\u0131z HTTP isteklerini almaya devam eder; QUIC \u00e7o\u011fu kurulumda istemci ile ters proxy aras\u0131ndaki katmanda sonland\u0131r\u0131l\u0131r. Ters proxy ile uygulama sunucusu aras\u0131ndaki ba\u011flant\u0131 HTTP\/1.1 veya HTTP\/2 olabilir.<\/p>\n<div class=\"aiw-callout aiw-callout-tip\">\n<p class=\"aiw-callout-label\">\u0130pucu<\/p>\n<p>Taray\u0131c\u0131 geli\u015ftirici ara\u00e7lar\u0131nda Network sekmesindeki Protocol s\u00fctununu a\u00e7\u0131n. h3 g\u00f6r\u00fcyorsan\u0131z istemci HTTP\/3 kullan\u0131yor; h2 g\u00f6r\u00fcyorsan\u0131z ba\u011flant\u0131 HTTP\/2 \u00fczerinden kurulmu\u015ftur.<\/p>\n<\/div>\n<h2 id=\"sunucuda-http-3-ve-quic-nasil-test-edilir\">Sunucuda HTTP\/3 ve QUIC nas\u0131l test edilir?<\/h2>\n<p>\u00d6nce alan ad\u0131n\u0131n do\u011fru IP adresine \u00e7\u00f6z\u00fcld\u00fc\u011f\u00fcn\u00fc ve sunucunun UDP 443&#8217;\u00fc dinledi\u011fini kontrol edin. DNS taraf\u0131nda bir <a href=\"https:\/\/www.vps.tc\/blog\/tr\/ip-adresi-nedir-ne-ise-yarar-nasil-ogrenilir\/\">IP Adresi Nedir?<\/a> kayna\u011f\u0131ndaki temel kontroller, QUIC i\u00e7in de ge\u00e7erlidir; yaln\u0131zca TCP eri\u015fiminin \u00e7al\u0131\u015fmas\u0131 UDP eri\u015fiminin de \u00e7al\u0131\u015ft\u0131\u011f\u0131n\u0131 g\u00f6stermez.<\/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, <code>ss<\/code> \u00e7\u0131kt\u0131s\u0131 UDP 443 dinleyicisini, <code>nft<\/code> \u00e7\u0131kt\u0131s\u0131 ise g\u00fcvenlik duvar\u0131 kurallar\u0131n\u0131 incelemeye yarar. \u00c7\u0131kt\u0131da yaln\u0131zca TCP 443 g\u00f6r\u00fcn\u00fcyorsa HTTP\/3 hen\u00fcz dinlenmiyor olabilir.<\/p>\n<p><code>curl<\/code> s\u00fcr\u00fcm\u00fcn\u00fcz HTTP\/3 destekliyorsa basit bir istemci testi yap\u0131labilir:<\/p>\n<pre><code>curl -I --http3 https:\/\/example.com<\/code><\/pre>\n<p>Komutun \u00e7al\u0131\u015fmas\u0131 i\u00e7in curl&#8217;\u00fcn HTTP\/3 destekli bir QUIC k\u00fct\u00fcphanesiyle derlenmi\u015f olmas\u0131 gerekir. <code>option --http3: the installed libcurl version doesn't support this<\/code> benzeri bir hata, do\u011frudan sunucunun hatal\u0131 oldu\u011funu kan\u0131tlamaz; \u00f6nce istemci yetene\u011fini do\u011frulay\u0131n.<\/p>\n<pre><code>curl -V<\/code><\/pre>\n<p>\u00c7\u0131kt\u0131daki <code>Features<\/code> sat\u0131r\u0131nda HTTP3 veya ilgili HTTP\/3 deste\u011fini aray\u0131n. Da\u011f\u0131t\u0131m depolar\u0131ndaki curl s\u00fcr\u00fcm\u00fc bu \u00f6zelli\u011fi i\u00e7ermiyorsa taray\u0131c\u0131 geli\u015ftirici ara\u00e7lar\u0131, <code>nghttp3<\/code> tabanl\u0131 istemciler veya sa\u011flay\u0131c\u0131n\u0131n resmi test ara\u00e7lar\u0131 kullan\u0131labilir.<\/p>\n<p>Taray\u0131c\u0131 taraf\u0131nda geli\u015ftirici ara\u00e7lar\u0131n\u0131n Network sekmesindeki Protocol s\u00fctununa bak\u0131n. <code>h3<\/code> veya <code>h3-29<\/code> gibi bir de\u011fer HTTP\/3 ba\u011flant\u0131s\u0131n\u0131, <code>h2<\/code> HTTP\/2&#8217;yi, <code>http\/1.1<\/code> ise eski HTTP s\u00fcr\u00fcm\u00fcn\u00fc g\u00f6sterir. Taray\u0131c\u0131 \u00f6nbelle\u011fi ve mevcut oturum ilk denemeyi etkileyebilece\u011fi i\u00e7in gizli pencere veya yeni profil ile de test yap\u0131n.<\/p>\n<p><strong>Ne yap\u0131lmal\u0131<\/strong> &#8211; curl deste\u011fini, DNS kay\u0131tlar\u0131n\u0131, UDP 443 firewall kural\u0131n\u0131 ve taray\u0131c\u0131daki protokol de\u011ferini ayn\u0131 test plan\u0131nda do\u011frulay\u0131n.<\/p>\n<h2 id=\"quic-kullanirken-hangi-portlar-ve-firewall-kurallari-gerekir\">QUIC kullan\u0131rken hangi portlar ve firewall kurallar\u0131 gerekir?<\/h2>\n<p>HTTP\/3 i\u00e7in yayg\u0131n sunucu portu UDP 443&#8217;t\u00fcr. TCP 443 ise HTTP\/2 ve HTTP\/1.1 geri d\u00f6n\u00fc\u015f\u00fc i\u00e7in a\u00e7\u0131k tutulmal\u0131d\u0131r. QUIC istemci taraf\u0131nda sabit bir kaynak portu kullanmaz; istemci i\u015fletim sistemi genellikle ge\u00e7ici bir UDP portu se\u00e7er.<\/p>\n<p>Bir VPS sa\u011flay\u0131c\u0131s\u0131n\u0131n g\u00fcvenlik grubu UDP 443&#8217;\u00fc engelliyorsa Nginx veya uygulama sunucusunda QUIC&#8217;i a\u00e7mak yeterli olmaz. Ayn\u0131 kontrol i\u015fletim sistemi firewall&#8217;\u0131, bulut g\u00fcvenlik grubu, edge proxy, CDN ve varsa kurumsal a\u011f cihazlar\u0131 i\u00e7in ayr\u0131 ayr\u0131 yap\u0131lmal\u0131d\u0131r.<\/p>\n<p>UDP trafi\u011fini s\u0131n\u0131rs\u0131z b\u0131rakmak da iyi bir g\u00fcvenlik politikas\u0131 de\u011fildir. Paket h\u0131z\u0131, ba\u011flant\u0131 say\u0131s\u0131 ve kaynak t\u00fcketimi izlenmelidir. QUIC ba\u011flant\u0131lar\u0131nda TLS el s\u0131k\u0131\u015fmas\u0131 ve kriptografik i\u015flemler CPU kullanabilir. DDoS korumas\u0131 gereken projelerde <a href=\"https:\/\/www.vps.tc\/blog\/tr\/ddos-saldirisi-nedir-vps-koruma-rehberi\/\">DDoS Sald\u0131r\u0131s\u0131 Nedir? VPS Koruma Rehberi<\/a> ba\u015fl\u0131\u011f\u0131ndaki genel a\u011f katman\u0131 kontrolleri QUIC i\u00e7in UDP boyutuyla geni\u015fletilmelidir.<\/p>\n<p>MTU ve par\u00e7alanma sorunlar\u0131 da g\u00f6z ard\u0131 edilmemeli. UDP paketlerinin yol \u00fczerinde par\u00e7alanmas\u0131, TCP&#8217;dekinden farkl\u0131 ar\u0131zalar olu\u015fturabilir. \u00d6zellikle t\u00fcnel, VPN veya kaps\u00fclleme kullan\u0131lan a\u011flarda PMTU davran\u0131\u015f\u0131n\u0131 ve kay\u0131p oran\u0131n\u0131 g\u00f6zlemleyin.<\/p>\n<div class=\"aiw-callout aiw-callout-warn\">\n<p class=\"aiw-callout-label\">Dikkat<\/p>\n<p>UDP 443&#039;\u00fc a\u00e7mak tek ba\u015f\u0131na HTTP\/3&#039;\u00fc \u00e7al\u0131\u015ft\u0131rmaz. Sunucu, reverse proxy, bulut g\u00fcvenlik grubu ve i\u015fletim sistemi firewall&#039;\u0131 ayn\u0131 trafi\u011fe izin vermelidir; TCP 443 fallback i\u00e7in kapat\u0131lmamal\u0131d\u0131r.<\/p>\n<\/div>\n<h2 id=\"quicin-hiz-avantaji-her-sitede-gorulur-mu\">QUIC&#8217;in h\u0131z avantaj\u0131 her sitede g\u00f6r\u00fcl\u00fcr m\u00fc?<\/h2>\n<p>QUIC&#8217;in en belirgin faydas\u0131 y\u00fcksek gecikmeli, paket kayb\u0131 ya\u015fayan veya mobil a\u011f de\u011fi\u015fiklikleri bulunan ba\u011flant\u0131larda ortaya \u00e7\u0131kabilir. \u00c7ok say\u0131da k\u00fc\u00e7\u00fck kayna\u011f\u0131n ayn\u0131 anda istendi\u011fi web sayfalar\u0131nda ba\u011f\u0131ms\u0131z ak\u0131\u015flar ve daha az el s\u0131k\u0131\u015fma gecikmeyi azaltabilir.<\/p>\n<p>Sunucuya yak\u0131n, kay\u0131ps\u0131z ve iyi \u00f6nbelleklenen bir sayfada fark k\u00fc\u00e7\u00fck kalabilir. Sayfa bir CDN&#8217;den veriliyor, HTML tek bir k\u00fc\u00e7\u00fck dosyadan olu\u015fuyor veya backend yan\u0131t\u0131 800 milisaniye s\u00fcr\u00fcyorsa ta\u015f\u0131ma protokol\u00fcndeki birka\u00e7 milisaniyelik kazan\u00e7 toplam s\u00fcreyi belirlemez.<\/p>\n<p>\u00d6l\u00e7\u00fcm s\u0131ras\u0131nda yaln\u0131zca TTFB&#8217;ye bakmak yeterli de\u011fildir. \u0130lk ba\u011flant\u0131, yeniden ba\u011flant\u0131, \u00f6nbellekli kaynaklar, kay\u0131p paket oran\u0131, p95 ve p99 gecikmeleri birlikte incelenmelidir. <a href=\"https:\/\/www.vps.tc\/blog\/tr\/vps-bant-genisligi-ihtiyacinizi-hesaplayin\/\">VPS Bant Geni\u015fli\u011fi Nedir? \u0130htiyac\u0131n\u0131z\u0131 Hesaplay\u0131n<\/a> i\u00e7eri\u011findeki kapasite hesab\u0131 da yard\u0131mc\u0131 olur; 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 anlat\u0131r?<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Protokol se\u00e7imi<\/td>\n<td>\u0130stemcilerin HTTP\/3&#8217;e ge\u00e7ip ge\u00e7medi\u011fini g\u00f6sterir.<\/td>\n<\/tr>\n<tr>\n<td>\u0130lk byte s\u00fcresi<\/td>\n<td>Ta\u015f\u0131ma gecikmesinin yan\u0131nda uygulama ve \u00f6nbellek performans\u0131n\u0131 da yans\u0131t\u0131r.<\/td>\n<\/tr>\n<tr>\n<td>p95\/p99 gecikme<\/td>\n<td>Ortalaman\u0131n gizledi\u011fi yava\u015f istemci grubunu g\u00f6r\u00fcn\u00fcr k\u0131lar.<\/td>\n<\/tr>\n<tr>\n<td>UDP paket kayb\u0131<\/td>\n<td>QUIC&#8217;in kay\u0131p kurtarma davran\u0131\u015f\u0131n\u0131 de\u011ferlendirmeye yard\u0131m eder.<\/td>\n<\/tr>\n<tr>\n<td>Hata ve fallback oran\u0131<\/td>\n<td>UDP ba\u015far\u0131s\u0131z oldu\u011funda TCP&#8217;ye d\u00f6n\u00fc\u015f\u00fcn sa\u011fl\u0131kl\u0131 olup olmad\u0131\u011f\u0131n\u0131 g\u00f6sterir.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Bir CDN kullan\u0131l\u0131yorsa HTTP\/3 \u00e7o\u011fu zaman origin sunucuda de\u011fil edge noktas\u0131nda sonland\u0131r\u0131l\u0131r. Bu durumda ziyaret\u00e7inin edge&#8217;e ba\u011flant\u0131s\u0131 QUIC olabilirken edge ile origin aras\u0131ndaki ba\u011flant\u0131 TCP kalabilir. Test raporunu haz\u0131rlarken hangi ba\u011flant\u0131 b\u00f6l\u00fcm\u00fcn\u00fcn \u00f6l\u00e7\u00fcld\u00fc\u011f\u00fcn\u00fc yaz\u0131n.<\/p>\n<p><strong>Ne yap\u0131lmal\u0131<\/strong> &#8211; HTTP\/2 ve HTTP\/3 i\u00e7in ayn\u0131 URL, ayn\u0131 i\u00e7erik ve benzer istemci ko\u015fullar\u0131yla p95 gecikmeyi kar\u015f\u0131la\u015ft\u0131r\u0131n.<\/p>\n<div class=\"aiw-callout aiw-callout-example\">\n<p class=\"aiw-callout-label\">\u00d6rnek<\/p>\n<p>Mobil a\u011fdan Wi-Fi&#039;a ge\u00e7en bir istemcinin IP adresi de\u011fi\u015fir. QUIC Connection ID ba\u011flant\u0131y\u0131 koruyabilirse yeniden TCP ve TLS kurulumu gerekmez; NAT veya firewall ba\u011flant\u0131y\u0131 engellerse istemci TCP fallback yoluna d\u00f6ner.<\/p>\n<\/div>\n<h2 id=\"quicin-dezavantajlari-ve-guvenlik-sinirlari-nelerdir\">QUIC&#8217;in dezavantajlar\u0131 ve g\u00fcvenlik s\u0131n\u0131rlar\u0131 nelerdir?<\/h2>\n<p>QUIC her altyap\u0131da sorunsuz \u00e7al\u0131\u015fmaz. Baz\u0131 eski g\u00fcvenlik duvarlar\u0131 ve a\u011f izleme sistemleri TCP trafi\u011fini ayr\u0131nt\u0131l\u0131 bi\u00e7imde tan\u0131rken UDP trafi\u011fini s\u0131n\u0131rlayabilir veya engelleyebilir. B\u00f6yle bir a\u011fda HTTP\/3 ba\u011flant\u0131s\u0131 kurulamaz; TCP fallback \u00e7al\u0131\u015fm\u0131yorsa kullan\u0131c\u0131 hata g\u00f6rebilir.<\/p>\n<p>G\u00f6zlemleme taraf\u0131nda da al\u0131\u015fkanl\u0131klar\u0131 de\u011fi\u015ftirmek gerekir. TCP ba\u011flant\u0131lar\u0131n\u0131 izleyen mevcut paneller, QUIC ak\u0131\u015flar\u0131n\u0131n durumunu tam g\u00f6stermeyebilir. Sunucu ve proxy&#8217;nin QUIC metrikleri, UDP paket kayb\u0131, handshake hatalar\u0131, ba\u011flant\u0131 g\u00f6\u00e7leri ve fallback oranlar\u0131 ayr\u0131ca toplanmal\u0131d\u0131r.<\/p>\n<p>0-RTT ba\u011flant\u0131 yeniden kurulurken gecikmeyi d\u00fc\u015f\u00fcrebilir. Fakat RFC 9001 ve TLS 1.3 modelinde 0-RTT verileri yeniden oynatma riskine a\u00e7\u0131kt\u0131r. Bu nedenle para transferi, sipari\u015f olu\u015fturma, parola de\u011fi\u015ftirme veya ba\u015fka yan etkili i\u015flemler 0-RTT verisiyle ko\u015fulsuz kabul edilmemelidir. \u0130dempotent GET istekleri bu \u00f6zellik i\u00e7in daha uygun adayd\u0131r.<\/p>\n<p>QUIC \u015fifreli oldu\u011fu i\u00e7in a\u011f y\u00f6neticileri i\u00e7eri\u011fi do\u011frudan inceleyemez; bu, kullan\u0131c\u0131 gizlili\u011fi a\u00e7\u0131s\u0131ndan olumlu olsa da hata ay\u0131klama ve politika uygulama y\u00f6ntemlerini etkiler. TLS anahtar g\u00fcnl\u00fckleme, u\u00e7 nokta metrikleri ve kontroll\u00fc paket analizi kurumun g\u00fcvenlik politikas\u0131na uygun tasarlanmal\u0131d\u0131r.<\/p>\n<p>HTTP\/3&#8217;\u00fc etkinle\u015ftirmek, k\u00f6t\u00fc yap\u0131land\u0131r\u0131lm\u0131\u015f uygulamay\u0131 h\u0131zland\u0131rmaz. Veritaban\u0131 sorgusu yava\u015fsa, resimler s\u0131k\u0131\u015ft\u0131r\u0131lmam\u0131\u015fsa veya \u00f6nbellek ba\u015fl\u0131klar\u0131 hatal\u0131ysa protokol de\u011fi\u015fikli\u011fi sorunu gizlemeye \u00e7al\u0131\u015f\u0131r. \u00d6nce <a href=\"https:\/\/www.vps.tc\/blog\/tr\/502-bad-gateway-hatasi-nedir-nasil-cozulur\/\">502 Bad Gateway Hatas\u0131 Nedir ve Nas\u0131l \u00c7\u00f6z\u00fcl\u00fcr?<\/a> gibi uygulama ve proxy ar\u0131zalar\u0131n\u0131n temel nedenlerini ay\u0131r\u0131n.<\/p>\n<div class=\"aiw-callout aiw-callout-field\">\n<p class=\"aiw-callout-label\">Sahadan not<\/p>\n<p>Bir gece test sunucusunda temizlik yaparken terminale yanl\u0131\u015f hostname ile ba\u011fland\u0131\u011f\u0131m\u0131 fark etmeden rm -rf komutunu haz\u0131rlad\u0131m. Prompt&#039;ta production ad\u0131n\u0131 g\u00f6r\u00fcnce \u00e7al\u0131\u015ft\u0131rmadan durdum; o g\u00fcnden beri y\u0131k\u0131c\u0131 komutlardan \u00f6nce hostname ve \u00e7al\u0131\u015fma dizinini ayr\u0131ca do\u011fruluyorum.<\/p>\n<\/div>\n<h2 id=\"quic-etkinlestirmeden-once-nasil-bir-gecis-plani-izlenir\">QUIC etkinle\u015ftirmeden \u00f6nce nas\u0131l bir ge\u00e7i\u015f plan\u0131 izlenir?<\/h2>\n<p>\u00dcretim sisteminde do\u011frudan UDP 443 a\u00e7\u0131p ba\u015far\u0131 beklemek yerine kademeli ge\u00e7i\u015f daha g\u00fcvenlidir. \u00d6nce sunucu yaz\u0131l\u0131m\u0131n\u0131n kullan\u0131lan s\u00fcr\u00fcm\u00fcnde HTTP\/3 deste\u011fini, TLS sertifikas\u0131n\u0131n durumunu ve kernel firewall kurallar\u0131n\u0131 do\u011frulay\u0131n. Sa\u011flay\u0131c\u0131n\u0131n y\u00fck dengeleyicisi veya CDN&#8217;i aradaysa onun QUIC deste\u011fi ayr\u0131ca kontrol edilmelidir.<\/p>\n<ol>\n<li>Alan ad\u0131n\u0131n A ve AAAA kay\u0131tlar\u0131n\u0131 do\u011frulay\u0131n.<\/li>\n<li>TCP 443 fallback eri\u015fimini koruyun.<\/li>\n<li>UDP 443&#8217;\u00fc g\u00fcvenlik gruplar\u0131nda ve nftables \u00fczerinde kontroll\u00fc olarak a\u00e7\u0131n.<\/li>\n<li>HTTP\/3 destekli sunucu veya reverse proxy yap\u0131land\u0131rmas\u0131n\u0131 test ortam\u0131nda deneyin.<\/li>\n<li>curl ve taray\u0131c\u0131 geli\u015ftirici ara\u00e7lar\u0131yla ger\u00e7ek protokol\u00fc do\u011frulay\u0131n.<\/li>\n<li>HTTP\/2&#8217;ye d\u00f6nen istemcilerin hata almad\u0131\u011f\u0131n\u0131 izleyin.<\/li>\n<li>Hata, gecikme, CPU ve UDP paket kayb\u0131 metriklerini kar\u015f\u0131la\u015ft\u0131r\u0131n.<\/li>\n<\/ol>\n<p>Bir alan ad\u0131nda HTTP\/3 \u00e7al\u0131\u015f\u0131rken ba\u015fka bir alt alan ad\u0131nda \u00e7al\u0131\u015fmamas\u0131 ola\u011fand\u0131r; her edge, proxy ve DNS katman\u0131 farkl\u0131 yap\u0131land\u0131r\u0131labilir. DNS de\u011fi\u015fikliklerini incelemek i\u00e7in <a href=\"https:\/\/www.vps.tc\/blog\/tr\/dns-probe-finished-nxdomain-hatasi-nasil-cozulur\/\">DNS_PROBE_FINISHED_NXDOMAIN Hatas\u0131 Nas\u0131l \u00c7\u00f6z\u00fcl\u00fcr?<\/a> i\u00e7eri\u011findeki temel yakla\u015f\u0131m kullan\u0131labilir, fakat QUIC sorunu i\u00e7in ayr\u0131ca UDP yolunu test etmek gerekir.<\/p>\n<p>Geri d\u00f6n\u00fc\u015f plan\u0131 basit olmal\u0131: UDP 443&#8217;\u00fc kapatmak veya HTTP\/3 ilan\u0131n\u0131 kald\u0131rmak, TCP 443 \u00fczerinden hizmeti s\u00fcrd\u00fcrmenize izin vermeli. QUIC&#8217;i a\u00e7madan \u00f6nceki HTTP\/2 \u00f6l\u00e7\u00fcmlerini saklay\u0131n; aksi halde h\u0131z iddias\u0131 kar\u015f\u0131la\u015ft\u0131r\u0131lamaz bir izlenime d\u00f6n\u00fc\u015f\u00fcr.<\/p>\n<p>Ama\u00e7 b\u00fct\u00fcn ziyaret\u00e7ileri zorla QUIC&#8217;e ge\u00e7irmek de\u011fildir. Uyumlu istemcilere HTTP\/3 sunmak, di\u011ferlerine HTTP\/2 veya HTTP\/1.1 vermek daha dayan\u0131kl\u0131 bir internet hizmeti sa\u011flar.<\/p>\n<p><strong>Ne yap\u0131lmal\u0131<\/strong> &#8211; HTTP\/3&#8217;\u00fc \u00f6nce \u00f6l\u00e7\u00fclebilir bir trafik diliminde yay\u0131nlay\u0131n ve fallback ile geri d\u00f6n\u00fc\u015f\u00fc ayn\u0131 g\u00fcn test edin.<\/p>\n<h2 id=\"quic-kurulumundan-once-sunlari-kontrol-edin\">QUIC Kurulumundan \u00d6nce \u015eunlar\u0131 Kontrol Edin<\/h2>\n<ul class=\"aiw-checklist\">\n<li>HTTP\/3 ve QUIC deste\u011fini kulland\u0131\u011f\u0131n\u0131z sunucu veya CDN s\u00fcr\u00fcm\u00fcnde do\u011frulay\u0131n.<\/li>\n<li>Alan ad\u0131n\u0131n A ve AAAA kay\u0131tlar\u0131n\u0131 test edin.<\/li>\n<li>UDP 443&#039;\u00fc sunucu, g\u00fcvenlik grubu ve firewall katmanlar\u0131nda kontroll\u00fc bi\u00e7imde a\u00e7\u0131n.<\/li>\n<li>TCP 443&#039;\u00fc HTTP\/2 ve HTTP\/1.1 fallback i\u00e7in a\u00e7\u0131k tutun.<\/li>\n<li>curl s\u00fcr\u00fcm\u00fcn\u00fcn HTTP\/3 deste\u011fiyle derlendi\u011fini curl -V \u00e7\u0131kt\u0131s\u0131ndan kontrol edin.<\/li>\n<li>Taray\u0131c\u0131 Network sekmesinde protokol\u00fcn ger\u00e7ekten h3 oldu\u011funu do\u011frulay\u0131n.<\/li>\n<li>p95 gecikme, CPU, paket kayb\u0131 ve fallback oranlar\u0131n\u0131 HTTP\/2 ile kar\u015f\u0131la\u015ft\u0131r\u0131n.<\/li>\n<\/ul>\n<div class=\"aiw-cta\">\n<p>Sunucuda HTTP\/3&#039;\u00fc a\u00e7madan \u00f6nce UDP 443, TCP fallback ve ger\u00e7ek istemci \u00f6l\u00e7\u00fcmlerini ayn\u0131 test plan\u0131na ekleyin. K\u00fc\u00e7\u00fck bir trafik dilimiyle ba\u015flay\u0131p metrikler do\u011fruland\u0131k\u00e7a kapsam\u0131 geni\u015fletmek daha g\u00fcvenlidir.<\/p>\n<p class=\"aiw-cta-action\"><a href=\"https:\/\/www.vps.tc\/tr\/vps\">VPS paketlerini inceleyin<\/a><\/p>\n<\/div>\n<h2 id=\"sik-sorulan-sorular\">S\u0131k Sorulan Sorular<\/h2>\n<div class=\"aiw-faq\">\n<details class=\"aiw-faq-item\" open>\n<summary>QUIC nedir, ne i\u015fe yarar?<\/summary>\n<p>QUIC, UDP \u00fczerinde \u00e7al\u0131\u015fan g\u00fcvenli bir ta\u015f\u0131ma protokol\u00fcd\u00fcr. TLS 1.3 \u015fifrelemesini, kay\u0131p paket kurtarmay\u0131, \u00e7oklu ak\u0131\u015flar\u0131 ve ba\u011flant\u0131 kimliklerini ayn\u0131 tasar\u0131mda birle\u015ftirir. HTTP\/3 bu protokol\u00fc kullan\u0131r. Ama\u00e7, \u00f6zellikle y\u00fcksek gecikmeli veya paket kayb\u0131 ya\u015fayan a\u011flarda ba\u011flant\u0131 kurulumu ve veri ak\u0131\u015f\u0131 davran\u0131\u015f\u0131n\u0131 iyile\u015ftirmektir.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>QUIC TCP&#039;den daha m\u0131 h\u0131zl\u0131d\u0131r?<\/summary>\n<p>Her ba\u011flant\u0131da otomatik olarak daha h\u0131zl\u0131 de\u011fildir. QUIC; daha k\u0131sa ba\u011flant\u0131 kurulumu, ba\u011f\u0131ms\u0131z ak\u0131\u015flar ve a\u011f de\u011fi\u015fimlerinde ba\u011flant\u0131y\u0131 koruyabilme sayesinde baz\u0131 senaryolarda avantaj sa\u011flar. Mobil a\u011flar, y\u00fcksek gecikme ve paket kayb\u0131 bu avantaj\u0131 g\u00f6r\u00fcn\u00fcr k\u0131labilir. Yak\u0131n ve kararl\u0131 a\u011flarda HTTP\/2 ile fark k\u00fc\u00e7\u00fck olabilir; karar ger\u00e7ek p95 ve p99 \u00f6l\u00e7\u00fcmlerine dayanmal\u0131d\u0131r.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>HTTP\/3 ile QUIC aras\u0131ndaki fark nedir?<\/summary>\n<p>QUIC bir ta\u015f\u0131ma protokol\u00fcd\u00fcr; HTTP\/3 ise HTTP istek ve yan\u0131tlar\u0131n\u0131 QUIC ak\u0131\u015flar\u0131 \u00fczerinde ta\u015f\u0131yan HTTP s\u00fcr\u00fcm\u00fcd\u00fcr. QUIC, UDP \u00fczerinde g\u00fcvenilirlik, \u015fifreleme ve ak\u0131\u015f y\u00f6netimi sa\u011flar. HTTP\/3 ise HTTP y\u00f6ntemleri, ba\u015fl\u0131klar\u0131 ve durum kodlar\u0131 gibi uygulama katman\u0131 kurallar\u0131n\u0131 tan\u0131mlar. Bu nedenle iki terim birlikte kullan\u0131lsa da ayn\u0131 katman\u0131 ifade etmez.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>QUIC hangi portu kullan\u0131r?<\/summary>\n<p>Web hizmetlerinde QUIC ve HTTP\/3 i\u00e7in yayg\u0131n port UDP 443&#039;t\u00fcr. TCP 443 de HTTP\/2 veya HTTP\/1.1 fallback ba\u011flant\u0131lar\u0131 i\u00e7in a\u00e7\u0131k tutulmal\u0131d\u0131r. \u0130stemci taraf\u0131nda kaynak portu genellikle ge\u00e7icidir. UDP 443&#039;\u00fcn a\u00e7\u0131k olmas\u0131; g\u00fcvenlik grubu, i\u015fletim sistemi firewall&#039;\u0131, reverse proxy ve CDN katmanlar\u0131n\u0131n da bu trafi\u011fi kabul etti\u011fi anlam\u0131na gelmez, her katman ayr\u0131ca kontrol edilmelidir.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>QUIC g\u00fcvenli mi?<\/summary>\n<p>QUIC, TLS 1.3 ile b\u00fct\u00fcnle\u015fik \u00e7al\u0131\u015ft\u0131\u011f\u0131 i\u00e7in ba\u011flant\u0131 trafi\u011fi \u015fifrelenir ve kimlik do\u011frulama mekanizmas\u0131 kullan\u0131l\u0131r. G\u00fcvenlik, hatal\u0131 sunucu yap\u0131land\u0131rmas\u0131n\u0131 veya DDoS riskini ortadan kald\u0131rmaz. Ayr\u0131ca 0-RTT verileri yeniden oynatma riskine a\u00e7\u0131kt\u0131r. Yan etki olu\u015fturan i\u015flemler 0-RTT verisiyle ko\u015fulsuz kabul edilmemeli; sertifika, firewall, rate limit ve izleme politikalar\u0131 birlikte uygulanmal\u0131d\u0131r.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>Bir web sitesinde HTTP\/3 nas\u0131l test edilir?<\/summary>\n<p>\u00d6nce UDP 443 eri\u015fimini, sunucu dinleyicisini ve firewall kurallar\u0131n\u0131 kontrol edin. HTTP\/3 destekli curl s\u00fcr\u00fcm\u00fcnde curl -I &#8211;http3 https:\/\/example.com komutunu \u00e7al\u0131\u015ft\u0131rabilirsiniz. Ard\u0131ndan taray\u0131c\u0131 geli\u015ftirici ara\u00e7lar\u0131nda Network sekmesindeki Protocol s\u00fctununa bak\u0131n; h3 HTTP\/3 ba\u011flant\u0131s\u0131n\u0131 g\u00f6sterir. curl HTTP\/3 desteklemiyorsa al\u0131nan istemci hatas\u0131 sunucunun hatal\u0131 oldu\u011funu tek ba\u015f\u0131na kan\u0131tlamaz.<\/p>\n<\/details>\n<\/div>\n<h2 id=\"kaynaklar\">Kaynaklar<\/h2>\n<ul class=\"aiw-sources\">\n<li><a href=\"https:\/\/www.rfc-editor.org\/rfc\/rfc9000\" target=\"_blank\" rel=\"noopener\">IETF 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\">IETF 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\">IETF RFC 9114 &#8211; HTTP\/3<\/a> \u2014 rfc-editor.org<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>QUIC, HTTP\/3&#8217;\u00fcn kulland\u0131\u011f\u0131 modern ta\u015f\u0131ma protokol\u00fcd\u00fcr. UDP 443, TLS 1.3, ba\u011f\u0131ms\u0131z ak\u0131\u015flar, ba\u011flant\u0131 g\u00f6\u00e7\u00fc ve sunucu testlerini ele al\u0131yoruz.<\/p>\n","protected":false},"author":2,"featured_media":791,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[873],"tags":[],"class_list":["post-793","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-teknoloji"],"lang":"tr","translations":{"tr":793,"en":794},"pll_sync_post":[],"_links":{"self":[{"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/posts\/793","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=793"}],"version-history":[{"count":1,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/posts\/793\/revisions"}],"predecessor-version":[{"id":795,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/posts\/793\/revisions\/795"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/media\/791"}],"wp:attachment":[{"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/media?parent=793"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/categories?post=793"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/tags?post=793"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}