{"id":281,"date":"2025-12-16T02:04:01","date_gmt":"2025-12-16T02:04:01","guid":{"rendered":"https:\/\/www.vps.tc\/blog\/internet-protokolleri-tcp-ipden-http-3e-derinlemesine-bakis\/"},"modified":"2026-09-25T09:13:15","modified_gmt":"2026-09-25T09:13:15","slug":"internet-protokolleri-tcp-ipden-http-3e-derinlemesine-bakis","status":"publish","type":"post","link":"https:\/\/www.vps.tc\/blog\/tr\/internet-protokolleri-tcp-ipden-http-3e-derinlemesine-bakis\/","title":{"rendered":"\u0130nternet Protokolleri: TCP\/IP&#8217;den HTTP\/3&#8217;e Derinlemesine Bak\u0131\u015f"},"content":{"rendered":"<div class=\"aiw-summary\" id=\"aiw-ozet\">\n<p class=\"aiw-summary-title\">H\u0131zl\u0131 \u00d6zet &#8211; \u0130nternet protokollerini ve HTTP\/3&#039;\u00fc anlama<\/p>\n<p>\u0130nternet ileti\u015fimi tek bir protokolden olu\u015fmaz; DNS, IP, TCP veya QUIC, TLS ve HTTP farkl\u0131 sorumluluklar\u0131 payla\u015f\u0131r. Katmanlar\u0131 ay\u0131rarak \u00f6l\u00e7\u00fcm yapmak, VPS ve web sunucusu sorunlar\u0131nda daha h\u0131zl\u0131 ve g\u00fcvenli te\u015fhis sa\u011flar.<\/p>\n<ul>\n<li><strong>Katmanlar\u0131 ay\u0131r\u0131n<\/strong> \u2014 DNS, IP, ta\u015f\u0131ma, TLS ve HTTP katmanlar\u0131n\u0131 ayr\u0131 test ederek varsay\u0131mlar\u0131 azalt\u0131n.<\/li>\n<li><strong>TCP&#039;yi do\u011fru konumland\u0131r\u0131n<\/strong> \u2014 TCP g\u00fcvenilir ve s\u0131ral\u0131 aktar\u0131m sa\u011flar, fakat kay\u0131p segmentler ayn\u0131 ba\u011flant\u0131daki ak\u0131\u015flar\u0131 bekletebilir.<\/li>\n<li><strong>UDP&#039;yi hafife almay\u0131n<\/strong> \u2014 UDP yal\u0131n bir ta\u015f\u0131ma sunar; g\u00fcvenilirlik ve h\u0131z kontrol\u00fcn\u00fc kullanan uygulama veya QUIC \u00fcstlenir.<\/li>\n<li><strong>HTTP\/2 s\u0131n\u0131r\u0131n\u0131 bilin<\/strong> \u2014 HTTP\/2 \u00e7oklama ve HPACK getirir, ancak TCP&#039;nin ta\u015f\u0131ma katman\u0131 kaynakl\u0131 beklemesini ortadan kald\u0131rmaz.<\/li>\n<li><strong>HTTP\/3&#039;\u00fc \u00f6l\u00e7erek a\u00e7\u0131n<\/strong> \u2014 HTTP\/3 QUIC ve UDP\/443 kullan\u0131r; istemci deste\u011fi, firewall ve geri d\u00f6n\u00fc\u015f yolu birlikte do\u011frulanmal\u0131d\u0131r.<\/li>\n<li><strong>G\u00fcvenli\u011fi katmanl\u0131 kurun<\/strong> \u2014 TLS 1.2\/1.3, anahtar tabanl\u0131 SSH, s\u0131n\u0131rl\u0131 portlar ve do\u011frulanm\u0131\u015f firewall kurallar\u0131 birlikte ele al\u0131nmal\u0131d\u0131r.<\/li>\n<\/ul>\n<\/div>\n<p class=\"aiw-lead\">Bir ba\u011flant\u0131 sorununun kayna\u011f\u0131 \u00e7o\u011fu zaman uygulama de\u011fildir. DNS yan\u0131t\u0131, IP rotas\u0131, TCP veya QUIC portu, TLS el s\u0131k\u0131\u015fmas\u0131 ve HTTP yan\u0131t\u0131 ayr\u0131 ayr\u0131 \u00f6l\u00e7\u00fclmelidir. HTTP\/3, TCP&#039;nin yerine QUIC&#039;i koyar; fakat UDP\/443 eri\u015fimi, TLS 1.3 ve istemci deste\u011fi olmadan tek ba\u015f\u0131na h\u0131z garantisi vermez.<\/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=\"#internet-protokolleri-dijital-dunyanin-gorunmez-iskeleti\">\u0130nternet Protokolleri: Dijital D\u00fcnyan\u0131n G\u00f6r\u00fcnmez \u0130skeleti<\/a><\/li>\n<li><a href=\"#ag-mimarisi-ve-tcp-ip-modelinin-temelleri\">A\u011f Mimarisi ve TCP\/IP Modelinin Temelleri<\/a><\/li>\n<li><a href=\"#tcp-ve-ip-internetin-kalbi-atiyor\">TCP ve IP: \u0130nternet&#039;in Kalbi At\u0131yor<\/a><\/li>\n<li><a href=\"#uygulama-katmani-protokolleri-ve-webin-evrimi-http-1-xten-http-3e\">Uygulama Katman\u0131 Protokolleri ve Web&#039;in Evrimi: HTTP\/1.x&#039;ten HTTP\/3&#039;e<\/a><\/li>\n<li><a href=\"#guvenlik-ve-protokoller-bir-sistem-yoneticisinin-onceligi\">G\u00fcvenlik ve Protokoller: Bir Sistem Y\u00f6neticisinin \u00d6nceli\u011fi<\/a><\/li>\n<li><a href=\"#protokol-sorunlarini-giderme-ve-izleme-pratik-yaklasimlar\">Protokol Sorunlar\u0131n\u0131 Giderme ve \u0130zleme: Pratik Yakla\u015f\u0131mlar<\/a><\/li>\n<li><a href=\"#gelecegin-protokolleri-ve-aglar-yenilikler-yolda\">Gelece\u011fin Protokolleri ve A\u011flar: Yenilikler Yolda<\/a><\/li>\n<li><a href=\"#son-soz-dijital-dunyanin-kilcal-damarlari\">Son S\u00f6z: Dijital D\u00fcnyan\u0131n K\u0131lcal Damarlar\u0131<\/a><\/li>\n<li><a href=\"#uygulama-kontrol-listesi\">Uygulama Kontrol Listesi<\/a><\/li>\n<li><a href=\"#sik-sorulan-sorular\">S\u0131k Sorulan Sorular<\/a><\/li>\n<\/ol>\n<\/div>\n<h2 id=\"internet-protokolleri-dijital-dunyanin-gorunmez-iskeleti\">\u0130nternet Protokolleri: Dijital D\u00fcnyan\u0131n G\u00f6r\u00fcnmez \u0130skeleti<\/h2>\n<p>Bir web sayfas\u0131 a\u00e7\u0131l\u0131rken yaln\u0131zca taray\u0131c\u0131 ile sunucu konu\u015fmaz. DNS ad\u0131 IP adresine \u00e7evirir, y\u00f6nlendiriciler paketleri ta\u015f\u0131r, TCP veya QUIC ak\u0131\u015f\u0131 y\u00f6netir, TLS veriyi \u015fifreler ve HTTP uygulama iste\u011fini tan\u0131mlar. Bu katmanlar\u0131 ay\u0131rabilmek, VPS \u00fczerinde ya\u015fanan ba\u011flant\u0131, gecikme ve g\u00fcvenlik sorunlar\u0131n\u0131 do\u011fru yerde aramay\u0131 sa\u011flar.<\/p>\n<p>\u0130nternet protokollerini bilmek, her paketin i\u00e7eri\u011fini ezberlemek anlam\u0131na gelmez. Hangi katman\u0131n hangi sorumlulu\u011fu ta\u015f\u0131d\u0131\u011f\u0131n\u0131 ve bir ar\u0131za s\u0131ras\u0131nda hangi \u00f6l\u00e7\u00fcm\u00fcn yap\u0131laca\u011f\u0131n\u0131 bilmek \u00e7o\u011fu durumda yeterlidir.<\/p>\n<div class=\"aiw-callout aiw-callout-warn\">\n<p class=\"aiw-callout-label\">Dikkat<\/p>\n<p>0-RTT ile gelen erken veriyi otomatik olarak g\u00fcvenilir kabul etmeyin. Yeniden oynatma riski nedeniyle \u00f6deme, durum de\u011fi\u015ftirme veya idempotent olmayan i\u015flemleri bu ak\u0131\u015fta kabul etmeyin.<\/p>\n<\/div>\n<h2 id=\"ag-mimarisi-ve-tcp-ip-modelinin-temelleri\">A\u011f Mimarisi ve TCP\/IP Modelinin Temelleri<\/h2>\n<p>\u0130nternet protokolleri, verilerin adreslenmesini, ta\u015f\u0131nmas\u0131n\u0131 ve i\u015flenmesini tan\u0131mlayan standartlard\u0131r. Bu standartlar katmanl\u0131 bir modelle birlikte \u00e7al\u0131\u015f\u0131r. OSI modeli yedi katmanl\u0131 bir referans \u00e7er\u00e7evesidir; pratikte kullan\u0131lan TCP\/IP modeli ise \u00e7o\u011funlukla d\u00f6rt katmanla anlat\u0131l\u0131r. Baz\u0131 kaynaklar fiziksel ve veri ba\u011flant\u0131s\u0131 katmanlar\u0131n\u0131 ay\u0131rarak be\u015f katmanl\u0131 g\u00f6sterim kullan\u0131r.<\/p>\n<h3>TCP\/IP Modelinin Katmanlar\u0131 ve G\u00f6revleri<\/h3>\n<ul>\n<li><strong>Uygulama Katman\u0131:<\/strong> HTTP, DNS, SMTP, SSH ve benzeri protokoller uygulamalar\u0131n a\u011f hizmetlerini kullanmas\u0131n\u0131 sa\u011flar. Veri bi\u00e7imi ve uygulama mesajlar\u0131n\u0131n anlam\u0131 bu katmanda belirlenir.<\/li>\n<li><strong>Ta\u015f\u0131ma Katman\u0131:<\/strong> Uygulamalar aras\u0131ndaki ak\u0131\u015f\u0131 y\u00f6netir. TCP s\u0131ral\u0131 ve g\u00fcvenilir aktar\u0131m sunarken UDP, QUIC gibi protokollerin temelini olu\u015fturan daha yal\u0131n datagram aktar\u0131m\u0131 sa\u011flar.<\/li>\n<li><strong>\u0130nternet Katman\u0131:<\/strong> IP paketlerinin kaynak ve hedef adreslerini kullanarak a\u011flar aras\u0131nda y\u00f6nlendirme yap\u0131l\u0131r. IPv4 ve IPv6 bu katman\u0131n ba\u015fl\u0131ca protokolleridir.<\/li>\n<li><strong>A\u011f Eri\u015fim Katman\u0131:<\/strong> Ethernet ve Wi-Fi gibi teknolojiler \u00fczerinden \u00e7er\u00e7evelerin iletilmesini, MAC adreslerini ve fiziksel ba\u011flant\u0131y\u0131 kapsar.<\/li>\n<\/ul>\n<p>Katmanlar birbirinden tamamen ba\u011f\u0131ms\u0131z de\u011fildir; fakat sorumluluklar\u0131n ayr\u0131lmas\u0131 te\u015fhisi kolayla\u015ft\u0131r\u0131r. \u00d6rne\u011fin bir DNS sorgusunun yan\u0131t vermemesi, uygulama sorunu gibi g\u00f6r\u00fcnse de UDP\/53 eri\u015fimi, y\u00f6nlendirme veya g\u00fcvenlik duvar\u0131 kural\u0131 kaynakl\u0131 olabilir.<\/p>\n<p><strong>Ne yap\u0131lmal\u0131<\/strong> &#8211; Bir ba\u011flant\u0131 sorununda uygulama loguna ge\u00e7meden \u00f6nce DNS \u00e7\u00f6z\u00fcmlemesini, IP eri\u015fimini, ilgili portu ve TLS el s\u0131k\u0131\u015fmas\u0131n\u0131 ayr\u0131 ayr\u0131 test edin.<\/p>\n<div class=\"aiw-callout aiw-callout-field\">\n<p class=\"aiw-callout-label\">Sahadan not<\/p>\n<p>Evde WireGuard&#039;\u0131 ilk kurdu\u011fum gece t\u00fcnel a\u00e7\u0131lmad\u0131. ss -lunp | grep 51820 \u00e7\u0131kt\u0131s\u0131 sunucunun UDP\/51820 dinledi\u011fini g\u00f6sterdi; tcpdump -ni eth0 udp port 51820 ise hi\u00e7 paket gelmedi\u011fini ortaya \u00e7\u0131kard\u0131. Sorun uygulamada de\u011fil, router \u00fczerindeki UDP y\u00f6nlendirmesindeydi.<\/p>\n<\/div>\n<h2 id=\"tcp-ve-ip-internetin-kalbi-atiyor\">TCP ve IP: \u0130nternet&#8217;in Kalbi At\u0131yor<\/h2>\n<p>TCP ve IP ayn\u0131 i\u015fi yapmaz. IP, paketlerin a\u011flar aras\u0131nda adreslenmesini ve y\u00f6nlendirilmesini sa\u011flar; TCP ise iki u\u00e7taki uygulamalar aras\u0131nda g\u00fcvenilir bir bayt ak\u0131\u015f\u0131 kurar. Bu ayr\u0131m, sorunun a\u011f yolunda m\u0131 yoksa uygulaman\u0131n dinledi\u011fi portta m\u0131 oldu\u011funu anlamak i\u00e7in kritiktir.<\/p>\n<h3>IP (Internet Protocol): Adresleme ve Y\u00f6nlendirme<\/h3>\n<p>IP paketleri kaynak ve hedef adreslerini ta\u015f\u0131r. Router&#8217;lar hedef adresi y\u00f6nlendirme tablolar\u0131yla kar\u015f\u0131la\u015ft\u0131r\u0131r ve paketi bir sonraki a\u011fa iletir. IP, teslimat garantisi vermez; paket kayb\u0131, s\u0131ra de\u011fi\u015fikli\u011fi veya yinelenen paketler i\u00e7in g\u00fcvenilirlik mekanizmas\u0131 ta\u015f\u0131ma katman\u0131na ya da uygulamaya b\u0131rak\u0131l\u0131r.<\/p>\n<ul>\n<li><strong>IPv4:<\/strong> 32 bit adres kullan\u0131r. <code>192.168.1.1<\/code> gibi adresler toplam 232 teorik adres alan\u0131na sahiptir; \u00f6zel a\u011flarda RFC 1918 kapsam\u0131ndaki <code>10.0.0.0\/8<\/code>, <code>172.16.0.0\/12<\/code> ve <code>192.168.0.0\/16<\/code> bloklar\u0131 kullan\u0131l\u0131r.<\/li>\n<li><strong>IPv6:<\/strong> 128 bit adres kullan\u0131r. \u00d6rnek bir dok\u00fcmantasyon adresi <code>2001:db8::1<\/code> bi\u00e7imindedir; <code>2001:db8::\/32<\/code> ger\u00e7ek y\u00f6nlendirme i\u00e7in de\u011fil, \u00f6rnekler i\u00e7in ayr\u0131lm\u0131\u015ft\u0131r.<\/li>\n<\/ul>\n<p>Bir sunucunun IP adresi tek ba\u015f\u0131na hizmetin \u00e7al\u0131\u015ft\u0131\u011f\u0131n\u0131 g\u00f6stermez. DNS kayd\u0131 do\u011fru olabilir, fakat g\u00fcvenlik duvar\u0131 ilgili portu engelliyor veya servis yaln\u0131zca <code>127.0.0.1<\/code> \u00fczerinde dinliyor olabilir.<\/p>\n<h3>TCP (Transmission Control Protocol): G\u00fcvenilir Ba\u011flant\u0131 ve Ak\u0131\u015f Kontrol\u00fc<\/h3>\n<p>TCP, ba\u011flant\u0131 odakl\u0131, s\u0131ral\u0131 ve g\u00fcvenilir bir aktar\u0131m sa\u011flar. Web&#8217;in HTTP\/1.1 ve HTTP\/2 s\u00fcr\u00fcmleri, SSH ve \u00e7o\u011fu veritaban\u0131 ba\u011flant\u0131s\u0131 TCP kullan\u0131r. Modern Linux sistemlerinde TCP soketlerini incelemek i\u00e7in eski <code>netstat<\/code> yerine genellikle <code>ss<\/code> tercih edilir.<\/p>\n<p>TCP&#8217;nin ba\u015fl\u0131ca mekanizmalar\u0131 \u015funlard\u0131r:<\/p>\n<ul>\n<li><strong>\u00dc\u00e7 y\u00f6nl\u00fc el s\u0131k\u0131\u015fma:<\/strong> Ba\u011flant\u0131 genellikle SYN, SYN-ACK ve ACK paketleriyle kurulur. Bu a\u015fama tamamlanmadan uygulama verisi normal ak\u0131\u015fa girmez.<\/li>\n<li><strong>S\u0131ral\u0131 teslimat:<\/strong> Segmentler s\u0131ra numaralar\u0131yla takip edilir; kay\u0131p segmentler yeniden g\u00f6nderilir.<\/li>\n<li><strong>Ak\u0131\u015f kontrol\u00fc:<\/strong> Al\u0131c\u0131n\u0131n ilan etti\u011fi pencere, g\u00f6ndericinin al\u0131c\u0131 tamponunu a\u015fmas\u0131n\u0131 \u00f6nler.<\/li>\n<li><strong>T\u0131kan\u0131kl\u0131k kontrol\u00fc:<\/strong> TCP, a\u011f\u0131n kapasitesini g\u00f6zlemleyerek g\u00f6nderim h\u0131z\u0131n\u0131 ayarlar. Bu, al\u0131c\u0131 tamponundan farkl\u0131 bir mekanizmad\u0131r.<\/li>\n<li><strong>Hata kontrol\u00fc:<\/strong> Sa\u011flama toplam\u0131 ve onay mekanizmalar\u0131 bozuk veya kay\u0131p verinin fark edilmesine yard\u0131mc\u0131 olur.<\/li>\n<\/ul>\n<p>TCP&#8217;nin g\u00fcvenilirli\u011fi gecikme maliyeti do\u011furur. Tek bir TCP ba\u011flant\u0131s\u0131nda kay\u0131p segmentin yeniden iletilmesi, ayn\u0131 ba\u011flant\u0131 \u00fczerindeki di\u011fer veri ak\u0131\u015flar\u0131n\u0131 da bekletebilir; HTTP\/2&#8217;nin uygulama katman\u0131ndaki \u00e7oklamas\u0131 bu ta\u015f\u0131ma katman\u0131 etkisini ortadan kald\u0131rmaz.<\/p>\n<h3>UDP (User Datagram Protocol): H\u0131z ve Basitlik<\/h3>\n<p>UDP ba\u011flant\u0131 kurma, s\u0131ralama ve yeniden iletim garantisi sunmayan bir ta\u015f\u0131ma protokol\u00fcd\u00fcr. DNS&#8217;in \u00e7o\u011fu sorgusu UDP\/53 kullan\u0131r; b\u00fcy\u00fck yan\u0131tlar veya aktar\u0131m ko\u015fullar\u0131 gerekti\u011finde TCP\/53&#8217;e ge\u00e7i\u015f g\u00f6r\u00fclebilir. Ger\u00e7ek zamanl\u0131 ses, oyun ve baz\u0131 t\u00fcnel protokolleri de UDP&#8217;nin d\u00fc\u015f\u00fck protokol y\u00fck\u00fcnden yararlan\u0131r.<\/p>\n<p>UDP&#8217;nin h\u0131zl\u0131 olmas\u0131 otomatik de\u011fildir. Uygulaman\u0131n paket kayb\u0131n\u0131, tekrarlar\u0131 ve h\u0131z kontrol\u00fcn\u00fc nas\u0131l ele ald\u0131\u011f\u0131 belirleyicidir. QUIC de UDP \u00fczerinde \u00e7al\u0131\u015f\u0131r, fakat g\u00fcvenilir ak\u0131\u015flar, \u015fifreleme ve t\u0131kan\u0131kl\u0131k kontrol\u00fcn\u00fc kendi protokol katman\u0131nda sa\u011flar.<\/p>\n<p><strong>Ne yap\u0131lmal\u0131<\/strong> &#8211; Bir portu test ederken yaln\u0131zca <code>ping<\/code> sonucuna g\u00fcvenmeyin; TCP i\u00e7in <code>ss<\/code> ve <code>nc<\/code>, UDP i\u00e7in servis loglar\u0131 ve <code>tcpdump<\/code> ile ger\u00e7ek trafi\u011fi do\u011frulay\u0131n.<\/p>\n<h2 id=\"uygulama-katmani-protokolleri-ve-webin-evrimi-http-1-xten-http-3e\">Uygulama Katman\u0131 Protokolleri ve Web&#8217;in Evrimi: HTTP\/1.x&#8217;ten HTTP\/3&#8217;e<\/h2>\n<p>Uygulama katman\u0131, ta\u015f\u0131nan verinin ne anlama geldi\u011fini belirler. HTTP bir web iste\u011finin y\u00f6ntemini, ba\u015fl\u0131klar\u0131n\u0131 ve g\u00f6vdesini tan\u0131mlar; DNS isim \u00e7\u00f6z\u00fcmlemesini, SMTP e-posta aktar\u0131m\u0131n\u0131, SSH ise uzak kabuk ve t\u00fcnel eri\u015fimini d\u00fczenler.<\/p>\n<h3>HTTP\/1.x: Web&#8217;in \u0130lk Ad\u0131mlar\u0131<\/h3>\n<p>HTTP\/1.0 ve HTTP\/1.1 metin tabanl\u0131 bir mesaj bi\u00e7imi kullan\u0131r. HTTP\/1.1 kal\u0131c\u0131 ba\u011flant\u0131lar ve par\u00e7a par\u00e7a aktar\u0131m gibi \u00f6zellikler getirdi; ancak tek ba\u011flant\u0131 \u00fczerindeki isteklerin s\u0131ral\u0131 i\u015flenmesi pratikte gecikme olu\u015fturabiliyordu.<\/p>\n<ul>\n<li><strong>Head-of-Line Blocking:<\/strong> Bir istek gecikti\u011finde ayn\u0131 ba\u011flant\u0131daki sonraki istekler bekleyebilirdi.<\/li>\n<li><strong>\u00c7ok say\u0131da TCP ba\u011flant\u0131s\u0131:<\/strong> Taray\u0131c\u0131lar gecikmeyi azaltmak i\u00e7in ayn\u0131 sunucuya birden fazla ba\u011flant\u0131 a\u00e7abiliyordu.<\/li>\n<li><strong>Ba\u015fl\u0131k tekrar\u0131:<\/strong> \u00c7erezler ve di\u011fer ba\u015fl\u0131klar her istekte yeniden ta\u015f\u0131nabiliyor, gereksiz veri olu\u015fturabiliyordu.<\/li>\n<\/ul>\n<h3>HTTP\/2: Performans Devrimi<\/h3>\n<p>HTTP\/2, RFC 9113 ile standartla\u015ft\u0131r\u0131lm\u0131\u015f ikili \u00e7er\u00e7eveleme ve \u00e7oklama yakla\u015f\u0131m\u0131n\u0131 kullan\u0131r. Genellikle TLS \u00fczerinden <code>h2<\/code> ALPN kimli\u011fiyle sunulur. Taray\u0131c\u0131 deste\u011fi pratikte HTTPS ile birlikte de\u011ferlendirilmelidir.<\/p>\n<ul>\n<li><strong>\u00c7oklama:<\/strong> Tek TCP ba\u011flant\u0131s\u0131 i\u00e7inde birden fazla istek ve yan\u0131t ba\u011f\u0131ms\u0131z ak\u0131\u015flar olarak ta\u015f\u0131n\u0131r.<\/li>\n<li><strong>Ba\u015fl\u0131k s\u0131k\u0131\u015ft\u0131rma:<\/strong> HPACK, tekrar eden ba\u015fl\u0131k alanlar\u0131n\u0131n daha verimli ta\u015f\u0131nmas\u0131n\u0131 sa\u011flar.<\/li>\n<li><strong>\u0130kili \u00e7er\u00e7eveleme:<\/strong> Mesajlar metin sat\u0131rlar\u0131 yerine \u00e7er\u00e7evelere ayr\u0131l\u0131r.<\/li>\n<li><strong>Sunucu itmesi:<\/strong> HTTP\/2 standard\u0131nda bulunur; ancak taray\u0131c\u0131 ve sunucu ekosisteminde s\u0131n\u0131rl\u0131 destek g\u00f6rd\u00fc\u011f\u00fc i\u00e7in g\u00fcncel kurulumlarda temel performans stratejisi olarak kullan\u0131lmamal\u0131d\u0131r.<\/li>\n<\/ul>\n<p>HTTP\/2, uygulama katman\u0131ndaki beklemeyi azalt\u0131r; TCP&#8217;nin kay\u0131p segment sonras\u0131 t\u00fcm ba\u011flant\u0131y\u0131 etkileyen davran\u0131\u015f\u0131n\u0131 de\u011fi\u015ftirmez. Bu ayr\u0131m, y\u00fcksek paket kayb\u0131 g\u00f6r\u00fclen mobil veya uzak ba\u011flant\u0131larda \u00f6nem kazan\u0131r.<\/p>\n<h3>HTTP\/3: Gelece\u011fin Web Protokol\u00fc ve QUIC<\/h3>\n<p>HTTP\/3, RFC 9114 ile standartla\u015ft\u0131r\u0131lm\u0131\u015ft\u0131r ve QUIC \u00fczerinde \u00e7al\u0131\u015f\u0131r. QUIC&#8217;in temel tan\u0131m\u0131 RFC 9000, TLS ile ba\u011flant\u0131s\u0131 ise RFC 9001 kapsam\u0131ndad\u0131r. HTTP\/3 i\u00e7in istemci ve sunucu aras\u0131nda \u00e7o\u011funlukla UDP\/443 eri\u015fimi gerekir; TCP\/443 a\u00e7\u0131k olsa bile UDP engelleniyorsa ba\u011flant\u0131 HTTP\/2 veya HTTP\/1.1&#8217;e d\u00fc\u015febilir.<\/p>\n<ul>\n<li><strong>UDP \u00fczerinde QUIC:<\/strong> QUIC, UDP&#8217;yi yaln\u0131zca ta\u015f\u0131ma kab\u0131 olarak kullan\u0131r; g\u00fcvenilir ak\u0131\u015f, yeniden iletim ve t\u0131kan\u0131kl\u0131k kontrol\u00fcn\u00fc kendi i\u00e7inde sa\u011flar.<\/li>\n<li><strong>Ak\u0131\u015f bazl\u0131 HOLB azalt\u0131m\u0131:<\/strong> Bir ak\u0131\u015ftaki kay\u0131p paket, ayn\u0131 ba\u011flant\u0131daki di\u011fer QUIC ak\u0131\u015flar\u0131n\u0131 TCP&#8217;deki gibi zorunlu olarak durdurmaz.<\/li>\n<li><strong>Entegre TLS 1.3:<\/strong> QUIC ba\u011flant\u0131lar\u0131 TLS 1.3 kullan\u0131r; TLS el s\u0131k\u0131\u015fmas\u0131 QUIC ba\u011flant\u0131 kurulumu ile birlikte ilerler.<\/li>\n<li><strong>0-RTT:<\/strong> Daha \u00f6nce kurulmu\u015f ba\u011flant\u0131larda erken veri g\u00f6nderilebilir. Bu veri yeniden oynatma riskine a\u00e7\u0131k olabilece\u011finden, sunucu 0-RTT isteklerini yaln\u0131zca idempotent i\u015flemlerde kabul etmelidir.<\/li>\n<li><strong>Ba\u011flant\u0131 ge\u00e7i\u015fi:<\/strong> Connection ID sayesinde istemcinin a\u011f adresi de\u011fi\u015fti\u011finde ba\u011flant\u0131 baz\u0131 durumlarda korunabilir; bu garanti her a\u011f cihaz\u0131 ve NAT davran\u0131\u015f\u0131 i\u00e7in mutlak de\u011fildir.<\/li>\n<\/ul>\n<p>HTTP\/3&#8217;\u00fc etkinle\u015ftirmek yaln\u0131zca bir web sunucusu direktifi eklemekten ibaret de\u011fildir. UDP\/443 g\u00fcvenlik duvar\u0131nda a\u00e7\u0131k olmal\u0131, sertifika ve ALPN do\u011fru sunulmal\u0131, istemci deste\u011fi izlenmeli ve TCP tabanl\u0131 geri d\u00f6n\u00fc\u015f yolu korunmal\u0131d\u0131r.<\/p>\n<p><strong>Ne yap\u0131lmal\u0131<\/strong> &#8211; HTTP\/3&#8217;\u00fc a\u00e7madan \u00f6nce <code>curl --http3<\/code> veya taray\u0131c\u0131 geli\u015ftirici ara\u00e7lar\u0131yla do\u011frulama yap\u0131n; UDP\/443 trafi\u011fini g\u00fcvenlik duvar\u0131 ve paket yakalama kay\u0131tlar\u0131nda ayr\u0131ca kontrol edin.<\/p>\n<div class=\"aiw-callout aiw-callout-tip\">\n<p class=\"aiw-callout-label\">\u0130pucu<\/p>\n<p>HTTP\/3&#039;\u00fc t\u00fcm alan adlar\u0131nda ayn\u0131 anda a\u00e7mak yerine \u00f6nce d\u00fc\u015f\u00fck riskli bir alan ad\u0131nda etkinle\u015ftirin. UDP\/443 eri\u015fimini, ALPN pazarl\u0131\u011f\u0131n\u0131 ve HTTP\/2&#039;ye geri d\u00f6n\u00fc\u015f\u00fc d\u0131\u015f a\u011flardan test edin.<\/p>\n<\/div>\n<h2 id=\"guvenlik-ve-protokoller-bir-sistem-yoneticisinin-onceligi\">G\u00fcvenlik ve Protokoller: Bir Sistem Y\u00f6neticisinin \u00d6nceli\u011fi<\/h2>\n<p>Bir protokol\u00fcn \u00e7al\u0131\u015fmas\u0131, g\u00fcvenli \u00e7al\u0131\u015ft\u0131\u011f\u0131 anlam\u0131na gelmez. Port eri\u015fimi, kimlik do\u011frulama, \u015fifreleme, sertifika do\u011frulamas\u0131 ve loglama birlikte de\u011ferlendirilmelidir.<\/p>\n<h3>TLS\/SSL ve HTTPS: Verilerin \u015eifreli Yolculu\u011fu<\/h3>\n<p>HTTPS, HTTP&#8217;nin TLS ile korunmu\u015f halidir. G\u00fcncel kurulumlarda TLS 1.2 ve \u00f6zellikle TLS 1.3 tercih edilir; TLS 1.0 ve TLS 1.1, RFC 8996 ile kullan\u0131mdan kald\u0131r\u0131lm\u0131\u015ft\u0131r. SSL ad\u0131 g\u00fcnl\u00fck dilde kalsa da SSLv2 ve SSLv3 g\u00fcvenli se\u00e7enekler de\u011fildir.<\/p>\n<p>TLS sertifikas\u0131 sunucu kimli\u011fini do\u011frular, \u015fifreleme anahtarlar\u0131n\u0131n kurulmas\u0131n\u0131 sa\u011flar ve aktar\u0131m\u0131n de\u011fi\u015ftirilmesini zorla\u015ft\u0131r\u0131r. Sertifika s\u00fcresi, hostname e\u015fle\u015fmesi, ara sertifikalar, SNI ve ALPN birlikte kontrol edilmelidir. <a href=\"https:\/\/www.vps.tc\/tr\/vps\">VPS<\/a> veya <a href=\"https:\/\/www.vps.tc\/tr\/turkiye-fiziksel-sunucu\">Dedicated Sunucu<\/a> y\u00f6netirken bu ayarlar\u0131n sorumlulu\u011fu altyap\u0131 y\u00f6neticisine aittir.<\/p>\n<h3>Di\u011fer G\u00fcvenlik Odakl\u0131 Protokoller<\/h3>\n<ul>\n<li><strong>SSH:<\/strong> Uzak kabuk, port y\u00f6nlendirme ve kimlik do\u011frulama i\u00e7in kullan\u0131l\u0131r. Parola yerine anahtar tabanl\u0131 eri\u015fim ve s\u0131n\u0131rl\u0131 kullan\u0131c\u0131 yetkileri tercih edilmelidir.<\/li>\n<li><strong>SFTP:<\/strong> SSH \u00fczerinden \u00e7al\u0131\u015fan dosya aktar\u0131m protokol\u00fcd\u00fcr; FTP&#8217;nin TLS&#8217;li bi\u00e7imiyle kar\u0131\u015ft\u0131r\u0131lmamal\u0131d\u0131r.<\/li>\n<li><strong>VPN protokolleri:<\/strong> IPsec, OpenVPN ve WireGuard farkl\u0131 kimlik do\u011frulama, anahtar y\u00f6netimi ve t\u00fcnel tasar\u0131mlar\u0131na sahiptir. WireGuard genellikle UDP kullan\u0131r; varsay\u0131lan portu 51820\/UDP&#8217;dir, fakat kurulum bunu de\u011fi\u015ftirebilir.<\/li>\n<\/ul>\n<p>SSH portunu de\u011fi\u015ftirmek tek ba\u015f\u0131na g\u00fcvenlik sa\u011flamaz. Daha etkili bir temel; g\u00fcncel paketler, anahtar tabanl\u0131 eri\u015fim, root giri\u015finin s\u0131n\u0131rland\u0131r\u0131lmas\u0131, MFA&#8217;n\u0131n uygun yerde kullan\u0131lmas\u0131, fail2ban ve nftables kurallar\u0131n\u0131n loglarla do\u011frulanmas\u0131d\u0131r.<\/p>\n<p><strong>Ne yap\u0131lmal\u0131<\/strong> &#8211; TLS s\u00fcr\u00fcmlerini, sertifika zincirini, SSH kimlik do\u011frulamas\u0131n\u0131 ve a\u00e7\u0131k portlar\u0131 d\u00fczenli aral\u0131klarla taray\u0131n; yapt\u0131\u011f\u0131n\u0131z her de\u011fi\u015fikli\u011fi geri alma ad\u0131m\u0131yla birlikte kaydedin.<\/p>\n<h2 id=\"protokol-sorunlarini-giderme-ve-izleme-pratik-yaklasimlar\">Protokol Sorunlar\u0131n\u0131 Giderme ve \u0130zleme: Pratik Yakla\u015f\u0131mlar<\/h2>\n<p>A\u011f te\u015fhisinde tek bir ara\u00e7 b\u00fct\u00fcn resmi g\u00f6stermez. \u00d6nce isim \u00e7\u00f6z\u00fcmlemeyi, ard\u0131ndan rota ve port eri\u015fimini, sonra TLS ve uygulama yan\u0131t\u0131n\u0131 ayr\u0131 katmanlarda \u00f6l\u00e7mek daha az varsay\u0131m \u00fcretir.<\/p>\n<ul>\n<li><strong><code>ping<\/code>:<\/strong> ICMP eri\u015fimi ve yakla\u015f\u0131k gecikmeyi \u00f6l\u00e7er. ICMP engellenmi\u015fse ba\u015far\u0131s\u0131z olmas\u0131, TCP veya HTTP&#8217;nin de ba\u015far\u0131s\u0131z oldu\u011fu anlam\u0131na gelmez.<\/li>\n<li><strong><code>mtr<\/code>:<\/strong> Traceroute yakla\u015f\u0131m\u0131n\u0131 canl\u0131 kay\u0131plar ve gecikme \u00f6l\u00e7\u00fcm\u00fcyle birle\u015ftirir. Son hopta kay\u0131p g\u00f6r\u00fcnmeden \u00f6nce ara hoplardaki ICMP rate limit&#8217;lerini yorumlay\u0131n.<\/li>\n<li><strong><code>dig<\/code>:<\/strong> DNS kay\u0131tlar\u0131n\u0131, sorgu t\u00fcr\u00fcn\u00fc ve yan\u0131t sunucusunu inceler. H\u0131zl\u0131 kontrol i\u00e7in <code>dig +short A example.com<\/code> ve <code>dig +short AAAA example.com<\/code> kullan\u0131labilir.<\/li>\n<li><strong><code>ss<\/code>:<\/strong> Dinleyen soketleri ve ba\u011flant\u0131 durumlar\u0131n\u0131 g\u00f6sterir. \u00d6rne\u011fin <code>ss -lntup<\/code>, TCP ve UDP dinleyicilerini s\u00fcre\u00e7 bilgisiyle listeler.<\/li>\n<li><strong><code>tcpdump<\/code>:<\/strong> Paketlerin ger\u00e7ekten aray\u00fcze ula\u015f\u0131p ula\u015fmad\u0131\u011f\u0131n\u0131 g\u00f6sterir. \u00dcretimde kapsam\u0131 daralt\u0131n; \u00f6rne\u011fin <code>tcpdump -ni eth0 port 443<\/code> \u00e7\u0131kt\u0131s\u0131n\u0131 s\u00fcre ve dosya boyutuyla s\u0131n\u0131rlay\u0131n.<\/li>\n<li><strong><code>curl<\/code>:<\/strong> HTTP durum kodu, y\u00f6nlendirme, TLS ve protokol pazarl\u0131\u011f\u0131n\u0131 kontrol eder. <code>curl -I --http2 https:\/\/example.com<\/code> veya desteklenen ortamda <code>curl --http3 -I https:\/\/example.com<\/code> kullan\u0131labilir.<\/li>\n<li><strong>G\u00fcvenlik duvar\u0131 loglar\u0131:<\/strong> nftables kurallar\u0131n\u0131n beklenen trafi\u011fi engelleyip engellemedi\u011fini g\u00f6sterir. Kural\u0131 de\u011fi\u015ftirmeden \u00f6nce saya\u00e7lar\u0131 ve mevcut konfig\u00fcrasyonu kaydedin.<\/li>\n<\/ul>\n<p>Bir servis yan\u0131t vermedi\u011finde \u00f6nce s\u00fcreci yeniden ba\u015flatmak cazip gelir. Daha g\u00fcvenli s\u0131ra; <code>systemctl status<\/code>, servis loglar\u0131, <code>ss<\/code> ile dinleme durumu, yerel ba\u011flant\u0131 testi ve d\u0131\u015f a\u011f testi \u015feklindedir. Log okumadan yeniden ba\u015flatmak, kan\u0131t\u0131 ortadan kald\u0131rabilir.<\/p>\n<p><strong>Ne yap\u0131lmal\u0131<\/strong> &#8211; Her a\u011f ar\u0131zas\u0131nda zaman damgas\u0131, istemci IP&#8217;si, hedef port, DNS yan\u0131t\u0131 ve \u00f6l\u00e7\u00fclen gecikmeyi kaydedin; te\u015fhis s\u0131ras\u0131nda ayn\u0131 testi farkl\u0131 a\u011flardan tekrarlay\u0131n.<\/p>\n<div class=\"aiw-callout aiw-callout-example\">\n<p class=\"aiw-callout-label\">\u00d6rnek<\/p>\n<p>Bir HTTPS ar\u0131zas\u0131nda \u015fu s\u0131ray\u0131 izleyin: dig +short A example.com, mtr -rw example.com, ss -lntp, ard\u0131ndan curl -Iv https:\/\/example.com. Her ad\u0131m farkl\u0131 bir katman\u0131 s\u0131nar.<\/p>\n<\/div>\n<h2 id=\"gelecegin-protokolleri-ve-aglar-yenilikler-yolda\">Gelece\u011fin Protokolleri ve A\u011flar: Yenilikler Yolda<\/h2>\n<p>HTTP\/3 art\u0131k yaln\u0131zca deneysel bir se\u00e7enek de\u011fildir; fakat her site i\u00e7in otomatik olarak daha h\u0131zl\u0131 olaca\u011f\u0131 da s\u00f6ylenemez. Paket kayb\u0131, istemci deste\u011fi, CDN davran\u0131\u015f\u0131, UDP eri\u015fimi ve sunucu y\u00fck\u00fc \u00f6l\u00e7\u00fclmeden yap\u0131lan ge\u00e7i\u015fler beklenen kazan\u0131m\u0131 vermeyebilir.<\/p>\n<ul>\n<li><strong>IPv6&#8217;n\u0131n yayg\u0131nla\u015fmas\u0131:<\/strong> \u00c7ift y\u0131\u011f\u0131n kurulumlar\u0131nda A ve AAAA kay\u0131tlar\u0131, y\u00f6nlendirme, firewall ve uygulama dinleme adresleri birlikte do\u011frulanmal\u0131d\u0131r.<\/li>\n<li><strong>\u015eifreleme ve kuantum sonras\u0131 haz\u0131rl\u0131k:<\/strong> Yeni algoritmalar\u0131n \u00fcretim sistemlerine eklenmesi standartlar, k\u00fct\u00fcphane deste\u011fi ve anahtar ya\u015fam d\u00f6ng\u00fcs\u00fcyle birlikte ele al\u0131nmal\u0131d\u0131r. TLS 1.3&#8217;\u00fc kapat\u0131p deneysel bir \u00e7\u00f6z\u00fcm eklemek g\u00fcvenlik plan\u0131 de\u011fildir.<\/li>\n<li><strong>A\u011f sanalla\u015ft\u0131rma ve programlanabilir a\u011flar:<\/strong> SDN, eBPF ve servis a\u011f\u0131 yakla\u015f\u0131mlar\u0131 g\u00f6zlemlenebilirli\u011fi art\u0131rabilir; karma\u015f\u0131kl\u0131k da ayn\u0131 \u00f6l\u00e7\u00fcde b\u00fcy\u00fcr. De\u011fi\u015fikliklerin kapsam\u0131, geri d\u00f6n\u00fc\u015f\u00fc ve \u00f6l\u00e7\u00fcm\u00fc \u00f6nceden tan\u0131mlanmal\u0131d\u0131r.<\/li>\n<\/ul>\n<p>Sistem y\u00f6neticileri i\u00e7in en de\u011ferli beceri yeni protokol adlar\u0131n\u0131 bilmekten \u00e7ok, protokol\u00fc \u00f6l\u00e7\u00fclebilir bir varsay\u0131mla devreye almakt\u0131r. HTTP\/3&#8217;\u00fc a\u00e7arken \u00f6nce bir alan ad\u0131nda etkinle\u015ftirmek, ger\u00e7ek istemci trafi\u011fini izlemek ve sorun halinde HTTP\/2&#8217;ye geri d\u00f6nmek kontroll\u00fc bir yakla\u015f\u0131md\u0131r.<\/p>\n<h2 id=\"son-soz-dijital-dunyanin-kilcal-damarlari\">Son S\u00f6z: Dijital D\u00fcnyan\u0131n K\u0131lcal Damarlar\u0131<\/h2>\n<p>TCP\/IP modeli, IP&#8217;nin y\u00f6nlendirme g\u00f6revini, TCP ve UDP&#8217;nin ta\u015f\u0131ma tercihlerini, TLS&#8217;in g\u00fcvenlik katman\u0131n\u0131 ve HTTP&#8217;nin uygulama mesaj\u0131n\u0131 birbirinden ay\u0131r\u0131r. HTTP\/3 ve QUIC bu yap\u0131y\u0131 ortadan kald\u0131rmaz; ta\u015f\u0131ma katman\u0131ndaki baz\u0131 s\u0131n\u0131rlamalar\u0131 farkl\u0131 bir tasar\u0131mla ele al\u0131r.<\/p>\n<p>Bir ba\u011flant\u0131 sorununda \u00f6nce katman\u0131 bulun, sonra \u00f6l\u00e7\u00fcn. <code>dig<\/code>, <code>mtr<\/code>, <code>ss<\/code>, <code>tcpdump<\/code> ve <code>curl<\/code> \u00e7o\u011fu VPS ar\u0131zas\u0131nda yeterli ba\u015flang\u0131\u00e7 setidir. Kendi altyap\u0131n\u0131z\u0131 kurarken <a href=\"https:\/\/www.vps.tc\/tr\/bulut-sunucu\">bulut sunucu<\/a> veya <a href=\"https:\/\/www.vps.tc\/tr\/vds-sanal-sunucu\">VDS sanal sunucu<\/a> se\u00e7iminin yan\u0131nda UDP eri\u015fimi, IPv6 deste\u011fi, firewall y\u00f6netimi ve \u00f6l\u00e7\u00fcm imkanlar\u0131n\u0131 da de\u011ferlendirin.<\/p>\n<h2 id=\"uygulama-kontrol-listesi\">Uygulama Kontrol Listesi<\/h2>\n<ul class=\"aiw-checklist\">\n<li>DNS i\u00e7in A ve AAAA kay\u0131tlar\u0131n\u0131 ayr\u0131 ayr\u0131 do\u011frulay\u0131n.<\/li>\n<li>Sunucunun ilgili TCP veya UDP portunda dinledi\u011fini kontrol edin.<\/li>\n<li>Firewall saya\u00e7lar\u0131n\u0131 ve loglar\u0131n\u0131 de\u011fi\u015fiklikten \u00f6nce kaydedin.<\/li>\n<li>TLS sertifikas\u0131n\u0131n s\u00fcresini, hostname&#039;ini ve zincirini do\u011frulay\u0131n.<\/li>\n<li>HTTP\/3 i\u00e7in UDP\/443 eri\u015fimini d\u0131\u015f a\u011fdan test edin.<\/li>\n<li>0-RTT isteklerini yaln\u0131zca g\u00fcvenli ve idempotent i\u015flemlerle s\u0131n\u0131rlay\u0131n.<\/li>\n<li>A\u011f de\u011fi\u015fikliklerini \u00f6nce staging veya d\u00fc\u015f\u00fck riskli bir alan ad\u0131nda deneyin.<\/li>\n<\/ul>\n<div class=\"aiw-cta\">\n<p>Sunucunuzdaki bir ba\u011flant\u0131 sorununu katmanlara ay\u0131rarak \u00f6l\u00e7\u00fcn; \u00f6zellikle DNS, UDP\/443 ve TLS sonu\u00e7lar\u0131n\u0131 ayr\u0131 kaydedin. \u0130sterseniz elde etti\u011finiz \u00e7\u0131kt\u0131lar\u0131 sonraki bak\u0131m notlar\u0131na ekleyerek te\u015fhis s\u00fcrecini tekrarlanabilir hale getirebilirsiniz.<\/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>TCP ile UDP aras\u0131ndaki temel fark nedir?<\/summary>\n<p>TCP ba\u011flant\u0131 kurar, veriyi s\u0131ral\u0131 ve g\u00fcvenilir bi\u00e7imde teslim etmeye \u00e7al\u0131\u015f\u0131r; kay\u0131p segmentleri yeniden g\u00f6nderir ve ak\u0131\u015f ile t\u0131kan\u0131kl\u0131k kontrol\u00fc uygular. UDP ise ba\u011flant\u0131 kurmadan datagram g\u00f6nderir, teslim veya s\u0131ra garantisi vermez. Bu nedenle DNS, ger\u00e7ek zamanl\u0131 medya ve baz\u0131 t\u00fcneller UDP&#039;den yararlanabilir; g\u00fcvenilirlik gerekiyorsa bunu uygulama veya QUIC sa\u011flamal\u0131d\u0131r.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>HTTP\/3 neden TCP yerine UDP kullan\u0131yor?<\/summary>\n<p>HTTP\/3, QUIC \u00fczerinden \u00e7al\u0131\u015f\u0131r ve QUIC UDP&#039;yi temel ta\u015f\u0131ma ortam\u0131 olarak kullan\u0131r. B\u00f6ylece QUIC, g\u00fcvenilir ak\u0131\u015flar\u0131 ve TLS 1.3 el s\u0131k\u0131\u015fmas\u0131n\u0131 kendi tasar\u0131m\u0131 i\u00e7inde y\u00f6netebilir. Ayr\u0131 ak\u0131\u015flardan birindeki paket kayb\u0131 di\u011fer ak\u0131\u015flar\u0131 TCP&#039;deki kadar do\u011frudan bekletmez. UDP yaln\u0131zca daha h\u0131zl\u0131 oldu\u011fu i\u00e7in se\u00e7ilmemi\u015ftir; protokol kontrol\u00fcn\u00fcn QUIC&#039;e ta\u015f\u0131nmas\u0131n\u0131 m\u00fcmk\u00fcn k\u0131lar.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>HTTP\/3 kullanmak i\u00e7in TCP\/443 kapat\u0131lmal\u0131 m\u0131?<\/summary>\n<p>Hay\u0131r. HTTP\/3 i\u00e7in UDP\/443 a\u00e7\u0131l\u0131r, fakat TCP\/443 genellikle korunur. \u0130stemci HTTP\/3 desteklemiyorsa veya UDP trafi\u011fi engelleniyorsa HTTP\/2 ya da HTTP\/1.1 \u00fczerinden geri d\u00f6n\u00fc\u015f gerekir. TCP&#039;yi kapatmak eri\u015filebilirli\u011fi azaltabilir. Firewall, CDN ve web sunucusu ayarlar\u0131nda iki ta\u015f\u0131ma yolunun davran\u0131\u015f\u0131n\u0131 ayr\u0131 ayr\u0131 test etmek daha g\u00fcvenlidir.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>HTTP\/2 sunucu itmesi h\u00e2l\u00e2 kullan\u0131lmal\u0131 m\u0131?<\/summary>\n<p>HTTP\/2 standard\u0131 sunucu itmesini tan\u0131mlasa da taray\u0131c\u0131 deste\u011fi ve pratik faydas\u0131 s\u0131n\u0131rl\u0131d\u0131r. Yanl\u0131\u015f tahmin edilen kaynaklar bant geni\u015fli\u011fi ve cache alan\u0131 t\u00fcketebilir. G\u00fcncel uygulamalarda do\u011fru cache ba\u015fl\u0131klar\u0131, s\u0131k\u0131\u015ft\u0131rma, kaynak boyutlar\u0131n\u0131n azalt\u0131lmas\u0131 ve HTTP\/2 \u00e7oklamas\u0131 daha \u00f6ng\u00f6r\u00fclebilir sonu\u00e7 verir. Sunucu itmesini a\u00e7madan \u00f6nce ger\u00e7ek istemci trafi\u011fi ve cache davran\u0131\u015f\u0131 \u00f6l\u00e7\u00fclmelidir.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>Bir web sitesinde HTTP\/3&#039;\u00fcn \u00e7al\u0131\u015ft\u0131\u011f\u0131 nas\u0131l do\u011frulan\u0131r?<\/summary>\n<p>\u00d6nce sunucunun UDP\/443 dinledi\u011fini ve firewall&#039;\u0131n trafi\u011fe izin verdi\u011fini kontrol edin. Ard\u0131ndan destekleyen bir curl s\u00fcr\u00fcm\u00fcnde curl &#8211;http3 -I https:\/\/example.com \u00e7al\u0131\u015ft\u0131r\u0131n veya taray\u0131c\u0131 a\u011f ara\u00e7lar\u0131nda kullan\u0131lan protokol\u00fc inceleyin. CDN kullan\u0131l\u0131yorsa origin ile istemci aras\u0131ndaki protokol\u00fcn farkl\u0131 olabilece\u011fini unutmay\u0131n; her iki ba\u011flant\u0131 ayr\u0131 do\u011frulanmal\u0131d\u0131r.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>TLS 1.0 ve TLS 1.1 neden devre d\u0131\u015f\u0131 b\u0131rak\u0131lmal\u0131?<\/summary>\n<p>TLS 1.0 ve TLS 1.1 g\u00fcncel g\u00fcvenlik ve kriptografi beklentilerini kar\u015f\u0131lamad\u0131\u011f\u0131 i\u00e7in RFC 8996 ile kullan\u0131mdan kald\u0131r\u0131ld\u0131. Modern web sunucular\u0131nda TLS 1.2 ve TLS 1.3 etkin tutulmal\u0131, eski istemciler i\u00e7in zorunlu istisna gerekiyorsa kapsam\u0131 ve s\u00fcresi belgelenmelidir. S\u00fcr\u00fcm de\u011fi\u015fikli\u011finden \u00f6nce istemci loglar\u0131n\u0131 inceleyin; aksi halde eski entegrasyonlar fark edilmeden kesilebilir.<\/p>\n<\/details>\n<\/div>\n","protected":false},"excerpt":{"rendered":"<p>\u0130nternet protokollerinin temel \u00e7al\u0131\u015fma prensiplerini, TCP\/IP modelinden ba\u015flayarak HTTP\/3&#8217;e kadar olan evrimini ve her bir protokol\u00fcn a\u011f ileti\u015fimindeki kritik rol\u00fcn\u00fc ke\u015ffedin. G\u00fcvenlik ve sorun giderme ipu\u00e7lar\u0131yla.<\/p>\n","protected":false},"author":1,"featured_media":280,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[17],"tags":[],"class_list":["post-281","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-genel"],"lang":"tr","translations":{"tr":281,"en":287},"pll_sync_post":[],"_links":{"self":[{"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/posts\/281","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\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/comments?post=281"}],"version-history":[{"count":7,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/posts\/281\/revisions"}],"predecessor-version":[{"id":929,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/posts\/281\/revisions\/929"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/media\/280"}],"wp:attachment":[{"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/media?parent=281"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/categories?post=281"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/tags?post=281"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}