{"id":2981,"date":"2026-10-22T22:43:24","date_gmt":"2026-10-22T19:43:24","guid":{"rendered":"https:\/\/saviorhost.com\/blog\/http3-quic-etkinlestirme\/"},"modified":"2026-10-22T23:21:10","modified_gmt":"2026-10-22T20:21:10","slug":"http3-quic-etkinlestirme","status":"publish","type":"post","link":"https:\/\/saviorhost.com\/blog\/http3-quic-etkinlestirme\/","title":{"rendered":"HTTP\/3 QUIC Etkinle\u015ftirme: Sunucuda TLS 1.3 Kurulumu"},"content":{"rendered":"<p>HTTP\/3 (QUIC) etkinle\u015ftirmenin ilk ko\u015fulu, sunucunuzda TLS 1.3&#8217;\u00fcn a\u00e7\u0131k olmas\u0131d\u0131r; HTTP\/3 yaln\u0131zca TLS 1.3 \u00fczerinden \u00e7al\u0131\u015f\u0131r. A\u015fa\u011f\u0131daki ad\u0131mlar Nginx, LiteSpeed ve Apache&#8217;de HTTP\/3 QUIC etkinle\u015ftirme s\u00fcrecini, firewall d\u00fczenlemelerini ve test y\u00f6ntemlerini uygulamal\u0131 olarak anlat\u0131r. S\u0131k yap\u0131lan hatalar\u0131 g\u00f6r\u00fcp \u00e7\u00f6z\u00fcmleri \u00f6\u011frenerek protokol\u00fc g\u00fcvenle devreye alabilirsiniz.<\/p>\n<p>HTTP\/3, web sayfalar\u0131n\u0131n daha h\u0131zl\u0131 y\u00fcklenmesini sa\u011flayan modern bir aktar\u0131m protokol\u00fcd\u00fcr. TCP yerine UDP \u00fczerinde \u00e7al\u0131\u015f\u0131r ve ba\u011flant\u0131 kurulum s\u00fcresini k\u0131salt\u0131r. \u00d6zellikle mobil kullan\u0131c\u0131larda ve paket kayb\u0131 olan a\u011flarda performans fark\u0131 belirginle\u015fir.<\/p>\n<div class=\"key-takeaways\">\n<p class=\"key-takeaways-title\"><strong>\u00d6nemli Noktalar<\/strong><\/p>\n<ul>\n<li>HTTP\/3 yaln\u0131zca TLS 1.3 ile \u00e7al\u0131\u015f\u0131r; sunucuda TLS 1.3 kapal\u0131ysa taray\u0131c\u0131lar otomatik olarak HTTP\/2&#8217;ye geri d\u00f6ner.<\/li>\n<li>Nginx 1.25 ve \u00fczeri s\u00fcr\u00fcmler HTTP\/3&#8217;\u00fc resmi olarak destekler, ancak mod\u00fcl\u00fcn derlenmi\u015f olmas\u0131 gerekir.<\/li>\n<li>UDP 443 portu hem sunucu g\u00fcvenlik duvar\u0131nda hem bulut sa\u011flay\u0131c\u0131 g\u00fcvenlik grubunda a\u00e7\u0131k olmal\u0131d\u0131r.<\/li>\n<li>Apache 2.4.x s\u00fcr\u00fcmlerinde yerle\u015fik HTTP\/3 deste\u011fi bulunmaz; ters proxy katman\u0131 en pratik \u00e7\u00f6z\u00fcmd\u00fcr.<\/li>\n<li><code>Alt-Svc<\/code> ba\u015fl\u0131\u011f\u0131, taray\u0131c\u0131ya HTTP\/3 deste\u011fini bildiren kritik bile\u015fendir.<\/li>\n<\/ul>\n<\/div>\n<h2 id=\"http3-quic-nedir\">HTTP\/3 ve QUIC Nedir, Neden TLS 1.3 Gerektirir?<\/h2>\n<p>HTTP\/3, internet taray\u0131c\u0131lar\u0131 ile sunucular aras\u0131nda veri aktarmak i\u00e7in kullan\u0131lan yeni nesil bir protokold\u00fcr. QUIC ise HTTP\/3&#8217;\u00fcn temelini olu\u015fturan ve UDP \u00fczerinde \u00e7al\u0131\u015fan ta\u015f\u0131ma protokol\u00fcd\u00fcr. Klasik HTTP\/2, TCP ba\u011flant\u0131lar\u0131 kurar; HTTP\/3 ise UDP paketleriyle \u00e7al\u0131\u015farak el s\u0131k\u0131\u015fma s\u00fcresini azalt\u0131r.<\/p>\n<figure class=\"wp-block-image size-large sm-inline-image\"><img loading=\"lazy\" decoding=\"async\" class=\"sm-ai-image wp-image-2984\" src=\"https:\/\/saviorhost.com\/blog\/wp-content\/uploads\/2026\/10\/http3-quic-etkinlestirme-sunucu-odasinda-http-mEc0.webp\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" srcset=\"https:\/\/saviorhost.com\/blog\/wp-content\/uploads\/2026\/10\/http3-quic-etkinlestirme-sunucu-odasinda-http-mEc0.webp 1024w, https:\/\/saviorhost.com\/blog\/wp-content\/uploads\/2026\/10\/http3-quic-etkinlestirme-sunucu-odasinda-http-mEc0-300x169.webp 300w, https:\/\/saviorhost.com\/blog\/wp-content\/uploads\/2026\/10\/http3-quic-etkinlestirme-sunucu-odasinda-http-mEc0-768x432.webp 768w\" alt=\"Sunucu odas\u0131nda HTTP\/3 trafi\u011fini g\u00f6steren parlak LED'li a\u011f anahtar\u0131\" width=\"1024\" height=\"576\" \/><\/figure>\n<p>HTTP\/3 ba\u011flant\u0131s\u0131 \u015fifreli olarak kurulur. Protokol\u00fcn tasar\u0131m\u0131 gere\u011fi TLS 1.3 kullan\u0131l\u0131r; bu nedenle sunucunuzda TLS 1.3&#8217;\u00fcn etkinle\u015ftirilmi\u015f olmas\u0131 ilk ad\u0131md\u0131r. TLS 1.3 kapal\u0131yken taray\u0131c\u0131lar HTTP\/3 ba\u011flant\u0131s\u0131 kuramaz ve otomatik olarak HTTP\/2 veya HTTP\/1.1&#8217;e geri d\u00f6ner.<\/p>\n<p>TLS 1.3&#8217;\u00fcn HTTP\/3 i\u00e7in zorunlu olmas\u0131n\u0131n teknik nedeni, QUIC&#8217;in el s\u0131k\u0131\u015fma s\u00fcrecini TLS oturumuyla birle\u015ftirmesidir. Bu birle\u015fik yap\u0131, ba\u011flant\u0131 kurulumunu tek gidi\u015f-d\u00f6n\u00fc\u015f s\u00fcresine indirir. Geleneksel TCP+TLS yap\u0131s\u0131nda ise \u00f6nce TCP el s\u0131k\u0131\u015fmas\u0131, ard\u0131ndan TLS el s\u0131k\u0131\u015fmas\u0131 yap\u0131l\u0131r; bu da iki veya \u00fc\u00e7 gidi\u015f-d\u00f6n\u00fc\u015f gerektirir.<\/p>\n<h2 id=\"on-kosullar\">\u00d6n Ko\u015fullar: Sunucu ve A\u011f Gereksinimleri<\/h2>\n<p>HTTP\/3 QUIC etkinle\u015ftirme \u00f6ncesinde a\u015fa\u011f\u0131daki ko\u015fullar\u0131 sa\u011flaman\u0131z gerekir. Bu ad\u0131m, sonraki yap\u0131land\u0131rma hatalar\u0131n\u0131 azalt\u0131r.<\/p>\n<ul>\n<li>Sunucuda root veya sudo yetkisine sahip bir kullan\u0131c\u0131 hesab\u0131.<\/li>\n<li>Nginx 1.25 veya \u00fczeri s\u00fcr\u00fcm ve derleme s\u0131ras\u0131nda <code>--with-http_v3_module<\/code> se\u00e7ene\u011fi. Alternatif olarak g\u00fcncel LiteSpeed veya OpenLiteSpeed.<\/li>\n<li>Ge\u00e7erli bir SSL\/TLS sertifikas\u0131. Let&#8217;s Encrypt veya ticari bir sertifika kullanabilirsiniz.<\/li>\n<li>Sunucunun g\u00fcvenlik duvar\u0131na ve varsa bulut sa\u011flay\u0131c\u0131 g\u00fcvenlik grubuna eri\u015fim.<\/li>\n<li>Alan ad\u0131n\u0131z\u0131n do\u011fru A veya AAAA kayd\u0131na sahip olmas\u0131.<\/li>\n<li>HTTP\/3 i\u00e7in UDP 443 portunun a\u00e7\u0131k olmas\u0131.<\/li>\n<\/ul>\n<p>Bu ko\u015fullar sa\u011fland\u0131\u011f\u0131nda yap\u0131land\u0131rma dosyalar\u0131n\u0131 d\u00fczenlemeye ge\u00e7ebilirsiniz. Sunucuya SSH ile ba\u011flanarak i\u015flemlere ba\u015flay\u0131n. Sunucunuzda temel g\u00fcvenlik ayarlar\u0131 hen\u00fcz yap\u0131lmad\u0131ysa <a href=\"https:\/\/saviorhost.com\/blog\/ubuntu-sunucu-kurulumu-guvenlik-ayarlari-2026\/\">Ubuntu 22.04 \/ 24.04 \u0130lk Sunucu Kurulumu ve Temel G\u00fcvenlik Ayarlar\u0131<\/a> yaz\u0131s\u0131n\u0131 incelemeniz faydal\u0131 olur.<\/p>\n<h2 id=\"nginx-http3\">Nginx&#8217;te HTTP\/3 ve TLS 1.3 Etkinle\u015ftirme<\/h2>\n<p>Nginx, HTTP\/3 deste\u011fini 1.25 s\u00fcr\u00fcm\u00fcnden itibaren resmi olarak sunar. Ancak da\u011f\u0131t\u0131m\u0131n\u0131z\u0131n deposundaki Nginx s\u00fcr\u00fcm\u00fc eski olabilir ve HTTP\/3 mod\u00fcl\u00fcn\u00fc i\u00e7ermeyebilir. \u00d6ncelikle mod\u00fcl\u00fcn derlenip derlenmedi\u011fini kontrol edin.<\/p>\n<pre><code class=\"language-bash\">nginx -V 2&gt;&amp;1 | grep -o -- '--with-http_v3_module'<\/code><\/pre>\n<p>Komut \u00e7\u0131kt\u0131s\u0131nda <code>--with-http_v3_module<\/code> ifadesini g\u00f6r\u00fcyorsan\u0131z Nginx HTTP\/3 destekliyordur. \u00c7\u0131kt\u0131 bo\u015fsa Nginx&#8217;in g\u00fcncel s\u00fcr\u00fcm\u00fcn\u00fc resmi depodan kurman\u0131z veya yeniden derlemeniz gerekir. G\u00fcncel s\u00fcr\u00fcm notlar\u0131 i\u00e7in <a href=\"https:\/\/nginx.org\" target=\"_blank\" rel=\"noopener nofollow\">nginx.org<\/a> adresini kontrol edin.<\/p>\n<figure class=\"wp-block-image size-large sm-inline-image\"><img loading=\"lazy\" decoding=\"async\" class=\"sm-ai-image wp-image-2985\" src=\"https:\/\/saviorhost.com\/blog\/wp-content\/uploads\/2026\/10\/http3-quic-etkinlestirme-gelistirici-terminalde-nginx-haE1.webp\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" srcset=\"https:\/\/saviorhost.com\/blog\/wp-content\/uploads\/2026\/10\/http3-quic-etkinlestirme-gelistirici-terminalde-nginx-haE1.webp 1024w, https:\/\/saviorhost.com\/blog\/wp-content\/uploads\/2026\/10\/http3-quic-etkinlestirme-gelistirici-terminalde-nginx-haE1-300x169.webp 300w, https:\/\/saviorhost.com\/blog\/wp-content\/uploads\/2026\/10\/http3-quic-etkinlestirme-gelistirici-terminalde-nginx-haE1-768x432.webp 768w\" alt=\"Geli\u015ftirici terminalde Nginx HTTP\/3 yap\u0131land\u0131rma dosyas\u0131n\u0131 d\u00fczenliyor\" width=\"1024\" height=\"576\" \/><\/figure>\n<p>Ad\u0131m 1: Site yap\u0131land\u0131rma dosyas\u0131n\u0131 a\u00e7\u0131n. Genellikle <code>\/etc\/nginx\/sites-available\/site.com.conf<\/code> veya <code>\/etc\/nginx\/conf.d\/site.com.conf<\/code> yolundad\u0131r.<\/p>\n<pre><code class=\"language-bash\">sudo nano \/etc\/nginx\/sites-available\/site.com.conf<\/code><\/pre>\n<p>Ad\u0131m 2: Mevcut <code>listen 443 ssl;<\/code> sat\u0131r\u0131n\u0131 bulun. Ayn\u0131 blokta HTTP\/3 i\u00e7in ikinci bir dinleme sat\u0131r\u0131 ekleyin.<\/p>\n<pre><code class=\"language-bash\">listen 443 ssl;\r\nlisten 443 quic reuseport;<\/code><\/pre>\n<p><code>reuseport<\/code> parametresi, ayn\u0131 portun hem TCP hem UDP i\u00e7in kullan\u0131labilmesini sa\u011flar. Bu sat\u0131r yoksa Nginx port \u00e7ak\u0131\u015fmas\u0131 nedeniyle ba\u015flat\u0131lamaz.<\/p>\n<p>Ad\u0131m 3: TLS protokol ayarlar\u0131n\u0131 kontrol edin. <code>ssl_protocols<\/code> sat\u0131r\u0131na <code>TLSv1.3<\/code> ekleyin. Mevcut istemcilerin ba\u011flant\u0131s\u0131n\u0131 kesmemek i\u00e7in TLS 1.2&#8217;yi de a\u00e7\u0131k b\u0131rakabilirsiniz.<\/p>\n<pre><code class=\"language-bash\">ssl_protocols TLSv1.2 TLSv1.3;<\/code><\/pre>\n<div class=\"sm-note sm-note-warning\"><strong>Dikkat:<\/strong> Bu sat\u0131rda <code>TLSv1.3<\/code> yoksa HTTP\/3 \u00e7al\u0131\u015fmaz. Taray\u0131c\u0131lar sessizce TCP tabanl\u0131 protokol\u00fc kullanmaya devam eder.<\/div>\n<p>Ad\u0131m 4: Taray\u0131c\u0131lara HTTP\/3 deste\u011fini bildiren <code>Alt-Svc<\/code> ba\u015fl\u0131\u011f\u0131n\u0131 ekleyin.<\/p>\n<pre><code class=\"language-bash\">add_header Alt-Svc 'h3=\":443\"; ma=86400';<\/code><\/pre>\n<p>Bu ba\u015fl\u0131k, taray\u0131c\u0131ya 86400 saniye boyunca HTTP\/3&#8217;\u00fcn 443 numaral\u0131 UDP portundan eri\u015filebilir oldu\u011funu s\u00f6yler. <code>ma<\/code> parametresi, taray\u0131c\u0131n\u0131n bu bilgiyi ne kadar s\u00fcreyle \u00f6nbelle\u011fe alaca\u011f\u0131n\u0131 belirler.<\/p>\n<p>Ad\u0131m 5: Yap\u0131land\u0131rmay\u0131 test edin ve Nginx&#8217;i yeniden y\u00fckleyin.<\/p>\n<pre><code class=\"language-bash\">sudo nginx -t\r\nsudo systemctl reload nginx<\/code><\/pre>\n<p>\u0130lk komut yap\u0131land\u0131rma hatalar\u0131n\u0131 g\u00f6sterir. \u0130kinci komut ise servisi kesintiye u\u011fratmadan yeni ayarlar\u0131 uygular.<\/p>\n<p>CentOS Web Panel \u00fczerinde \u00e7al\u0131\u015f\u0131yorsan\u0131z, Nginx HTTP\/3 ayarlar\u0131n\u0131 CWP \u00f6zelinde anlatan <a href=\"https:\/\/saviorhost.com\/blog\/centos-web-panel-icin-nginx-ile-http-3-ve-quic-nasil-aktif-edilir\/\">CentOS Web Panel i\u00e7in Nginx ile HTTP\/3 ve QUIC Nas\u0131l Aktif Edilir?<\/a> yaz\u0131s\u0131na g\u00f6z atabilirsiniz.<\/p>\n<h2 id=\"apache-http3\">Apache&#8217;de HTTP\/3 Deste\u011fi ve Ters Proxy \u00c7\u00f6z\u00fcm\u00fc<\/h2>\n<p>Apache HTTP Server&#8217;\u0131n kararl\u0131 2.4.x s\u00fcr\u00fcmlerinde resmi HTTP\/3 deste\u011fi bulunmaz. Bu nedenle yaln\u0131zca Apache \u00fczerinde tam HTTP\/3 QUIC etkinle\u015ftirme \u015fu anda yayg\u0131n bir pratik de\u011fildir. Apache kullan\u0131c\u0131lar\u0131 i\u00e7in en sa\u011flam \u00e7\u00f6z\u00fcm, TLS 1.3&#8217;\u00fc etkinle\u015ftirip HTTP\/3&#8217;\u00fc Nginx veya LiteSpeed gibi bir ters proxy katman\u0131na devretmektir.<\/p>\n<p>Apache&#8217;de TLS 1.3&#8217;\u00fc a\u00e7mak i\u00e7in SSL mod\u00fcl\u00fcn\u00fcn etkin oldu\u011fundan emin olun ve site yap\u0131land\u0131rma dosyas\u0131nda \u015fu sat\u0131rlar\u0131 d\u00fczenleyin.<\/p>\n<pre><code class=\"language-bash\">SSLProtocol TLSv1.2 TLSv1.3\r\nSSLCipherSuite HIGH:!aNULL:!MD5<\/code><\/pre>\n<p>Bu ayar, Apache&#8217;nin TLS 1.2 ve TLS 1.3 ba\u011flant\u0131lar\u0131n\u0131 kabul etmesini sa\u011flar. TLS 1.3, HTTP\/3&#8217;e ge\u00e7i\u015fin temel ta\u015f\u0131d\u0131r. Apache&#8217;yi ters proxy arkas\u0131na al\u0131rken 443 numaral\u0131 portu Nginx&#8217;in y\u00f6netmesine izin verirsiniz. B\u00f6ylece Nginx HTTP\/3&#8217;\u00fc sunarken Apache de PHP ve dinamik i\u00e7erikleri i\u015fleyebilir.<\/p>\n<figure class=\"wp-block-image size-large sm-inline-image\"><img loading=\"lazy\" decoding=\"async\" class=\"sm-ai-image wp-image-2986\" src=\"https:\/\/saviorhost.com\/blog\/wp-content\/uploads\/2026\/10\/http3-quic-etkinlestirme-nginxin-apache-onunde-PVwy.webp\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" srcset=\"https:\/\/saviorhost.com\/blog\/wp-content\/uploads\/2026\/10\/http3-quic-etkinlestirme-nginxin-apache-onunde-PVwy.webp 1024w, https:\/\/saviorhost.com\/blog\/wp-content\/uploads\/2026\/10\/http3-quic-etkinlestirme-nginxin-apache-onunde-PVwy-300x169.webp 300w, https:\/\/saviorhost.com\/blog\/wp-content\/uploads\/2026\/10\/http3-quic-etkinlestirme-nginxin-apache-onunde-PVwy-768x432.webp 768w\" alt=\"Nginx'in Apache \u00f6n\u00fcnde ters proxy olarak konumland\u0131\u011f\u0131 a\u011f ak\u0131\u015f \u015femas\u0131\" width=\"1024\" height=\"576\" \/><\/figure>\n<p>CentOS Web Panel \u00fczerinde Apache TLS 1.3 ayarlar\u0131 i\u00e7in <a href=\"https:\/\/saviorhost.com\/blog\/centos-web-panel-cwp-apachede-tls-1-3-nasil-etkinlestirilir\/\">CentOS Web Panel (CWP) Apache&#8217;de TLS 1.3 Nas\u0131l Etkinle\u015ftirilir?<\/a> yaz\u0131s\u0131 faydal\u0131 olacakt\u0131r.<\/p>\n<h2 id=\"litespeed-quic\">LiteSpeed ve OpenLiteSpeed&#8217;de QUIC A\u00e7ma<\/h2>\n<p>LiteSpeed Web Server ve OpenLiteSpeed, HTTP\/3 deste\u011fini yerle\u015fik olarak sunar. Panel \u00fczerinden QUIC&#8217;i etkinle\u015ftirmek birka\u00e7 ad\u0131m s\u00fcrer.<\/p>\n<ol>\n<li>WebAdmin konsoluna giri\u015f yap\u0131n.<\/li>\n<li><strong>Configuration &gt; Server &gt; General<\/strong> b\u00f6l\u00fcm\u00fcne gidin.<\/li>\n<li><strong>Enable QUIC<\/strong> se\u00e7ene\u011fini <strong>Yes<\/strong> olarak i\u015faretleyin.<\/li>\n<li>Listener ayarlar\u0131nda UDP portunun 443 olarak tan\u0131ml\u0131 oldu\u011funu do\u011frulay\u0131n.<\/li>\n<li>SSL\/TLS sekmesinde TLS 1.3&#8217;\u00fcn etkin oldu\u011funu kontrol edin.<\/li>\n<li>Ayarlar\u0131 kaydedip Graceful restart yap\u0131n.<\/li>\n<\/ol>\n<p>LiteSpeed&#8217;de QUIC a\u00e7\u0131ld\u0131\u011f\u0131nda <code>Alt-Svc<\/code> ba\u015fl\u0131\u011f\u0131 otomatik olarak y\u00f6netilir. Yine de a\u011f katman\u0131nda UDP 443 portunun a\u00e7\u0131k olmas\u0131 gerekir. LiteSpeed&#8217;in QUIC deste\u011fi, Nginx&#8217;e k\u0131yasla daha az yap\u0131land\u0131rma ad\u0131m\u0131 gerektirdi\u011fi i\u00e7in panel tabanl\u0131 y\u00f6netim tercih eden kullan\u0131c\u0131lar i\u00e7in pratiktir.<\/p>\n<h2 id=\"firewall-dns\">Firewall ve DNS Ayarlar\u0131<\/h2>\n<p>HTTP\/3&#8217;\u00fcn \u00e7al\u0131\u015fabilmesi i\u00e7in yaln\u0131zca TCP 443 de\u011fil, UDP 443 portunun da a\u00e7\u0131k olmas\u0131 gerekir. \u00c7o\u011fu sunucuda TCP 443 zaten a\u00e7\u0131kt\u0131r; ancak UDP 443 genellikle kapal\u0131d\u0131r. Bu, HTTP\/3&#8217;\u00fcn sessizce devre d\u0131\u015f\u0131 kalmas\u0131n\u0131n en yayg\u0131n nedenidir.<\/p>\n<p>Ubuntu ve UFW kullan\u0131yorsan\u0131z a\u015fa\u011f\u0131daki komutlar\u0131 \u00e7al\u0131\u015ft\u0131r\u0131n.<\/p>\n<pre><code class=\"language-bash\">sudo ufw allow 443\/tcp\r\nsudo ufw allow 443\/udp\r\nsudo ufw reload<\/code><\/pre>\n<p>Firewalld kullanan sistemlerde ise \u015fu komutlar\u0131 uygulay\u0131n.<\/p>\n<pre><code class=\"language-bash\">sudo firewall-cmd --permanent --add-service=https\r\nsudo firewall-cmd --permanent --add-port=443\/udp\r\nsudo firewall-cmd --reload<\/code><\/pre>\n<figure class=\"wp-block-image size-large sm-inline-image\"><img loading=\"lazy\" decoding=\"async\" class=\"sm-ai-image wp-image-2987\" src=\"https:\/\/saviorhost.com\/blog\/wp-content\/uploads\/2026\/10\/http3-quic-etkinlestirme-ag-yoneticisi-guvenlik-ImEU.webp\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" srcset=\"https:\/\/saviorhost.com\/blog\/wp-content\/uploads\/2026\/10\/http3-quic-etkinlestirme-ag-yoneticisi-guvenlik-ImEU.webp 1024w, https:\/\/saviorhost.com\/blog\/wp-content\/uploads\/2026\/10\/http3-quic-etkinlestirme-ag-yoneticisi-guvenlik-ImEU-300x169.webp 300w, https:\/\/saviorhost.com\/blog\/wp-content\/uploads\/2026\/10\/http3-quic-etkinlestirme-ag-yoneticisi-guvenlik-ImEU-768x432.webp 768w\" alt=\"A\u011f y\u00f6neticisi g\u00fcvenlik duvar\u0131nda UDP 443 kural\u0131n\u0131 kontrol ediyor\" width=\"1024\" height=\"576\" \/><\/figure>\n<p>Bulut sunucu kullan\u0131yorsan\u0131z sa\u011flay\u0131c\u0131n\u0131z\u0131n g\u00fcvenlik grubunda da UDP 443 kural\u0131n\u0131 eklemeniz gerekir. Ayr\u0131ca sunucu bir NAT veya y\u00fck dengeleyici arkas\u0131ndaysa UDP trafi\u011finin do\u011fru y\u00f6nlendirildi\u011finden emin olun. Baz\u0131 y\u00fck dengeleyiciler UDP passthrough&#8217;u varsay\u0131lan olarak desteklemez; bu durumda sa\u011flay\u0131c\u0131n\u0131z\u0131n dok\u00fcmantasyonunu kontrol etmeniz gerekir.<\/p>\n<p>DNS taraf\u0131nda \u00f6zel bir kay\u0131t de\u011fi\u015fikli\u011fi gerekmez. Ancak CDN kullan\u0131yorsan\u0131z HTTP\/3 ayar\u0131 genellikle CDN taraf\u0131nda yap\u0131l\u0131r. \u00d6rne\u011fin Cloudflare&#8217;de HTTP\/3 varsay\u0131lan olarak a\u00e7\u0131kt\u0131r; k\u00f6ken sunucuda da UDP 443 a\u00e7\u0131ksa u\u00e7tan uca QUIC kullan\u0131labilir.<\/p>\n<h2 id=\"http3-test\">HTTP\/3&#8217;\u00fc Test Etme ve Do\u011frulama<\/h2>\n<p>Yap\u0131land\u0131rma sonras\u0131 HTTP\/3&#8217;\u00fcn ger\u00e7ekten \u00e7al\u0131\u015f\u0131p \u00e7al\u0131\u015fmad\u0131\u011f\u0131n\u0131 do\u011frulaman\u0131z gerekir. En h\u0131zl\u0131 y\u00f6ntem, g\u00fcncel bir curl s\u00fcr\u00fcm\u00fc ile HTTP\/3 iste\u011fi g\u00f6ndermektir.<\/p>\n<pre><code class=\"language-bash\">curl --http3 -I https:\/\/ornek.com<\/code><\/pre>\n<p>Komut \u00e7\u0131kt\u0131s\u0131nda <code>HTTP\/3 200<\/code> gibi bir yan\u0131t g\u00f6r\u00fcyorsan\u0131z protokol aktif demektir. curl&#8217;\u00fcn\u00fcz HTTP\/3 deste\u011fi i\u00e7ermiyorsa g\u00fcncel s\u00fcr\u00fcm\u00fc <a href=\"https:\/\/curl.se\" target=\"_blank\" rel=\"noopener nofollow\">curl.se<\/a> adresinden edinebilirsiniz.<\/p>\n<p>Nginx yap\u0131land\u0131rmas\u0131n\u0131 h\u0131zl\u0131ca do\u011frulamak i\u00e7in \u015fu komutu da kullanabilirsiniz.<\/p>\n<pre><code class=\"language-bash\">nginx -T | grep -E 'listen.*quic|Alt-Svc'<\/code><\/pre>\n<p>Taray\u0131c\u0131da ise Chrome veya Edge geli\u015ftirici ara\u00e7lar\u0131n\u0131 a\u00e7\u0131n. <strong>Network<\/strong> sekmesinde <strong>Protocol<\/strong> s\u00fctununu g\u00f6r\u00fcn\u00fcr hale getirin. \u0130ste\u011fin protokol\u00fc <code>h3<\/code> olarak g\u00f6r\u00fcn\u00fcyorsa HTTP\/3 ba\u015far\u0131yla kullan\u0131l\u0131yor demektir.<\/p>\n<p>Sayfa h\u0131z\u0131ndaki dolayl\u0131 etkiyi g\u00f6rmek i\u00e7in <a href=\"https:\/\/saviorhost.com\/blog\/ttfb-ilk-bayt-suresi-nedir-google-seo-icin-sunucu-yanit-suresi-nasil-dusurulur\/\">TTFB Nedir? Google SEO \u0130\u00e7in Sunucu Yan\u0131t S\u00fcresini D\u00fc\u015f\u00fcrmenin 5 Yolu<\/a> yaz\u0131s\u0131n\u0131 inceleyebilirsiniz.<\/p>\n<div class=\"sm-note\"><strong>\u0130pucu:<\/strong> Test s\u0131ras\u0131nda taray\u0131c\u0131 \u00f6nbelle\u011fini temizleyin. Taray\u0131c\u0131lar <code>Alt-Svc<\/code> bilgisini \u00f6nbelle\u011fe ald\u0131\u011f\u0131 i\u00e7in eski sonu\u00e7lar g\u00f6rebilirsiniz.<\/div>\n<h2 id=\"sorun-giderme\">S\u0131k Kar\u015f\u0131la\u015f\u0131lan Hatalar ve \u00c7\u00f6z\u00fcmleri<\/h2>\n<p>HTTP\/3 kurulumunda ortaya \u00e7\u0131kan sorunlar genellikle mod\u00fcl eksikli\u011fi, port kapal\u0131l\u0131\u011f\u0131 veya ba\u015fl\u0131k eksikli\u011finden kaynaklan\u0131r. A\u015fa\u011f\u0131daki tablo yayg\u0131n hatalar\u0131 \u00f6zetler.<\/p>\n<div class=\"sm-table-wrap\">\n<table>\n<thead>\n<tr>\n<th>Hata Belirtisi<\/th>\n<th>Olas\u0131 Neden<\/th>\n<th>\u00c7\u00f6z\u00fcm<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><code>unknown directive \"http3\"<\/code><\/td>\n<td>Eski Nginx s\u00fcr\u00fcm\u00fc veya mod\u00fcl eksik<\/td>\n<td>Nginx&#8217;i g\u00fcncelleyip <code>listen ... quic<\/code> sat\u0131r\u0131n\u0131 kullan\u0131n<\/td>\n<\/tr>\n<tr>\n<td><code>bind() failed<\/code> veya <code>Address already in use<\/code><\/td>\n<td><code>reuseport<\/code> eksik<\/td>\n<td>Dinleme sat\u0131r\u0131na <code>reuseport<\/code> ekleyin<\/td>\n<\/tr>\n<tr>\n<td>curl: <code>option --http3 is unknown<\/code><\/td>\n<td>curl s\u00fcr\u00fcm\u00fc eski<\/td>\n<td>HTTP\/3 destekli g\u00fcncel curl kurun<\/td>\n<\/tr>\n<tr>\n<td>Taray\u0131c\u0131 s\u00fcrekli TCP kullan\u0131yor<\/td>\n<td>UDP 443 kapal\u0131 veya <code>Alt-Svc<\/code> yok<\/td>\n<td>Firewall kural\u0131n\u0131 ve ba\u015fl\u0131k sat\u0131r\u0131n\u0131 kontrol edin<\/td>\n<\/tr>\n<tr>\n<td>TLS el s\u0131k\u0131\u015fma hatas\u0131<\/td>\n<td><code>ssl_protocols<\/code> sat\u0131r\u0131nda TLS 1.3 yok<\/td>\n<td>Protokol listesine <code>TLSv1.3<\/code> ekleyin<\/td>\n<\/tr>\n<tr>\n<td>HTTP\/3 \u00e7al\u0131\u015f\u0131yor ancak performans art\u0131\u015f\u0131 yok<\/td>\n<td>CDN veya ters proxy HTTP\/3&#8217;\u00fc desteklemiyor<\/td>\n<td>Ara katmanlar\u0131n UDP 443 passthrough yapt\u0131\u011f\u0131n\u0131 do\u011frulay\u0131n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<p>Bu hatalar\u0131 \u00e7\u00f6zd\u00fckten sonra Nginx veya LiteSpeed servisini yeniden y\u00fckleyin ve test ad\u0131m\u0131n\u0131 tekrarlay\u0131n. Sorun devam ediyorsa sunucu loglar\u0131n\u0131 inceleyin; Nginx i\u00e7in <code>\/var\/log\/nginx\/error.log<\/code> dosyas\u0131 genellikle ipucu verir.<\/p>\n<h2 id=\"hangi-yontem\">Hangi Y\u00f6ntemi Se\u00e7melisiniz?<\/h2>\n<p>Nginx kullan\u0131yorsan\u0131z ve sunucunuzda g\u00fcncel s\u00fcr\u00fcm kuruluysa, Nginx HTTP\/3 en yayg\u0131n ve iyi belgelenmi\u015f y\u00f6ntemdir. LiteSpeed veya OpenLiteSpeed kullan\u0131yorsan\u0131z panel \u00fczerinden QUIC&#8217;i a\u00e7mak birka\u00e7 dakika s\u00fcrer. Apache kullan\u0131yorsan\u0131z k\u0131sa vadede TLS 1.3&#8217;\u00fc etkinle\u015ftirip HTTP\/3 katman\u0131n\u0131 Nginx&#8217;e devretmeniz en pratik \u00e7\u00f6z\u00fcmd\u00fcr.<\/p>\n<p>De\u011fi\u015fiklikleri canl\u0131ya almadan \u00f6nce test ortam\u0131nda deneyin ve mevcut yap\u0131land\u0131rman\u0131n yede\u011fini al\u0131n. Kurulum sonras\u0131 <code>curl --http3<\/code> ile do\u011frulama yapmay\u0131 atlamay\u0131n. HTTP\/3&#8217;\u00fcn sa\u011flad\u0131\u011f\u0131 h\u0131z avantaj\u0131, \u00f6zellikle mobil trafi\u011fi yo\u011fun olan sitelerde ve uzak co\u011frafi konumlardan eri\u015filen sunucularda daha belirgin hissedilir.<\/p>\n<h2 id=\"sss\">S\u0131k\u00e7a Sorulan Sorular<\/h2>\n<h3 id=\"http-3u-etkinlestirmeden-once-tls-1-3-zorunlu-mu\">HTTP\/3&#8217;\u00fc etkinle\u015ftirmeden \u00f6nce TLS 1.3 zorunlu mu?<\/h3>\n<p>Evet. HTTP\/3 protokol\u00fc el s\u0131k\u0131\u015fmas\u0131n\u0131 TLS 1.3 ile yapar. Sunucuda TLS 1.3 kapal\u0131ysa taray\u0131c\u0131lar HTTP\/3 ba\u011flant\u0131s\u0131 kuramaz ve TCP tabanl\u0131 protokol\u00fc kullan\u0131r.<\/p>\n<h3 id=\"udp-443u-acmazsam-ne-olur\">UDP 443&#8217;\u00fc a\u00e7mazsam ne olur?<\/h3>\n<p>Taray\u0131c\u0131lar QUIC ba\u011flant\u0131s\u0131 kuramaz ve otomatik olarak TCP 443 \u00fczerinden HTTP\/2 veya HTTP\/1.1&#8217;e geri d\u00f6ner. Site \u00e7al\u0131\u015fmaya devam eder ancak HTTP\/3&#8217;\u00fcn h\u0131z avantaj\u0131ndan yararlanamazs\u0131n\u0131z.<\/p>\n<h3 id=\"http-3-seo-siralamasini-dogrudan-yukseltir-mi\">HTTP\/3 SEO s\u0131ralamas\u0131n\u0131 do\u011frudan y\u00fckseltir mi?<\/h3>\n<p>HTTP\/3 do\u011frudan bir s\u0131ralama sinyali de\u011fildir. Ancak sayfa y\u00fckleme s\u00fcresini d\u00fc\u015f\u00fcrerek kullan\u0131c\u0131 deneyimini ve dolayl\u0131 olarak SEO performans\u0131n\u0131 iyile\u015ftirebilir.<\/p>\n<h3 id=\"paylasimli-hosting-kullaniyorsam-http-3u-kendim-etkinlestirebilir-miyim\">Payla\u015f\u0131ml\u0131 hosting kullan\u0131yorsam HTTP\/3&#8217;\u00fc kendim etkinle\u015ftirebilir miyim?<\/h3>\n<p>Payla\u015f\u0131ml\u0131 <a class=\"sm-cta-link\" href=\"https:\/\/saviorhost.com\/linux-web-hosting\">hosting<\/a> ortamlar\u0131nda sunucu yap\u0131land\u0131rmas\u0131na eri\u015fiminiz olmad\u0131\u011f\u0131 i\u00e7in HTTP\/3&#8217;\u00fc kendiniz etkinle\u015ftiremezsiniz. Hosting sa\u011flay\u0131c\u0131n\u0131z\u0131n HTTP\/3 deste\u011fi sunup sunmad\u0131\u011f\u0131n\u0131 kontrol etmeniz gerekir.<\/p>\n<h3 id=\"http-3u-etkinlestirdikten-sonra-eski-tarayicilar-siteye-erisemez-mi\">HTTP\/3&#8217;\u00fc etkinle\u015ftirdikten sonra eski taray\u0131c\u0131lar siteye eri\u015femez mi?<\/h3>\n<p>Hay\u0131r. HTTP\/3 desteklemeyen taray\u0131c\u0131lar otomatik olarak HTTP\/2 veya HTTP\/1.1 \u00fczerinden ba\u011flan\u0131r. Protokol geriye d\u00f6n\u00fck uyumluluk i\u00e7in tasarlanm\u0131\u015ft\u0131r; hi\u00e7bir kullan\u0131c\u0131 eri\u015fim kayb\u0131 ya\u015famaz.<\/p>\n<div class=\"sm-related-posts\" style=\"background: #f8fafc; border: 1px solid #e2e8f0; padding: 20px; border-radius: 8px; margin-top: 30px; clear: both;\">\n<p class=\"sm-related-posts-title\" style=\"margin-top: 0; color: #1e293b;\"><strong>\u0130lgili yaz\u0131lar<\/strong><\/p>\n<ul style=\"margin-bottom: 0; padding-left: 20px;\">\n<li><a href=\"https:\/\/saviorhost.com\/blog\/centos-web-panel-icin-nginx-ile-http-3-ve-quic-nasil-aktif-edilir\/\">CentOS Web Panel i\u00e7in Nginx ile HTTP\/3 ve QUIC Nas\u0131l Aktif Edilir?<\/a><\/li>\n<\/ul>\n<\/div>\n","protected":false},"excerpt":{"rendered":"<p>HTTP\/3 QUIC etkinle\u015ftirme i\u00e7in Nginx, LiteSpeed ve Apache&#8217;de TLS 1.3 kurulumunu ad\u0131m ad\u0131m uygulay\u0131n; UDP 443, firewall ve test ad\u0131mlar\u0131n\u0131 \u00f6\u011frenin.<\/p>\n","protected":false},"author":1,"featured_media":2989,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[66],"tags":[],"class_list":["post-2981","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-nginx"],"_links":{"self":[{"href":"https:\/\/saviorhost.com\/blog\/wp-json\/wp\/v2\/posts\/2981","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/saviorhost.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/saviorhost.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/saviorhost.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/saviorhost.com\/blog\/wp-json\/wp\/v2\/comments?post=2981"}],"version-history":[{"count":4,"href":"https:\/\/saviorhost.com\/blog\/wp-json\/wp\/v2\/posts\/2981\/revisions"}],"predecessor-version":[{"id":2990,"href":"https:\/\/saviorhost.com\/blog\/wp-json\/wp\/v2\/posts\/2981\/revisions\/2990"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/saviorhost.com\/blog\/wp-json\/wp\/v2\/media\/2989"}],"wp:attachment":[{"href":"https:\/\/saviorhost.com\/blog\/wp-json\/wp\/v2\/media?parent=2981"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/saviorhost.com\/blog\/wp-json\/wp\/v2\/categories?post=2981"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/saviorhost.com\/blog\/wp-json\/wp\/v2\/tags?post=2981"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}