{"id":939,"date":"2026-09-25T15:46:16","date_gmt":"2026-09-25T15:46:16","guid":{"rendered":"https:\/\/www.vps.tc\/blog\/?p=939"},"modified":"2026-09-25T10:00:05","modified_gmt":"2026-09-25T10:00:05","slug":"cdn-nedir-web-sitesini-nasil-hizlandirir","status":"publish","type":"post","link":"https:\/\/www.vps.tc\/blog\/tr\/cdn-nedir-web-sitesini-nasil-hizlandirir\/","title":{"rendered":"CDN Nedir? Web Sitesini Nas\u0131l H\u0131zland\u0131r\u0131r?"},"content":{"rendered":"<div class=\"aiw-summary\" id=\"aiw-ozet\">\n<p class=\"aiw-summary-title\">H\u0131zl\u0131 \u00d6zet &#8211; CDN ve Web Sitesi H\u0131z\u0131<\/p>\n<p>CDN, web i\u00e7eri\u011fini ziyaret\u00e7iye yak\u0131n edge sunucularda \u00f6nbelle\u011fe alarak origin sunucunun y\u00fck\u00fcn\u00fc ve a\u011f gecikmesini azalt\u0131r. Do\u011fru cache kurallar\u0131 kadar DNS, HTTPS ve cache temizleme plan\u0131 da gerekir.<\/p>\n<ul>\n<li><strong>CDN tan\u0131m\u0131<\/strong> \u2014 \u0130\u00e7erik Da\u011f\u0131t\u0131m A\u011f\u0131, statik veya uygun dinamik yan\u0131tlar\u0131 farkl\u0131 co\u011frafi noktalardan sunar.<\/li>\n<li><strong>H\u0131zlanma nedeni<\/strong> \u2014 Ziyaret\u00e7i i\u00e7eri\u011fi uzak origin yerine kendisine daha yak\u0131n bir edge sunucudan alabilir.<\/li>\n<li><strong>Uygun i\u00e7erik<\/strong> \u2014 CSS, JavaScript, g\u00f6rseller, fontlar ve s\u00fcr\u00fcmlenmi\u015f dosyalar CDN i\u00e7in iyi adaylard\u0131r.<\/li>\n<li><strong>Cache s\u0131n\u0131r\u0131<\/strong> \u2014 Oturum, sepet, y\u00f6netim paneli ve ki\u015fiselle\u015ftirilmi\u015f yan\u0131tlar varsay\u0131lan olarak cache edilmemelidir.<\/li>\n<li><strong>DNS ve HTTPS<\/strong> \u2014 Alan ad\u0131 CDN&#039;e y\u00f6nlendirilirken MX, TXT ve CAA kay\u0131tlar\u0131 korunmal\u0131; origin ba\u011flant\u0131s\u0131 da HTTPS olmal\u0131d\u0131r.<\/li>\n<li><strong>\u0130zlenecek \u00f6l\u00e7\u00fcm<\/strong> \u2014 Cache hit oran\u0131, origin yan\u0131t s\u00fcresi, hata kodlar\u0131 ve b\u00f6lgesel gecikme birlikte takip edilmelidir.<\/li>\n<\/ul>\n<\/div>\n<p class=\"aiw-lead\">CDN, web sitesi dosyalar\u0131n\u0131 ziyaret\u00e7iye yak\u0131n da\u011f\u0131t\u0131m sunucular\u0131nda \u00f6nbelle\u011fe alarak h\u0131zland\u0131r\u0131r. Statik i\u00e7erik cache hit oldu\u011funda istek origin sunucuya gitmez; a\u011f gecikmesi, TLS ve uygulama y\u00fck\u00fc azal\u0131r. Ancak CDN veritaban\u0131n\u0131 veya yava\u015f kodu kendili\u011finden d\u00fczeltmez; do\u011fru cache, DNS ve HTTPS ayar\u0131 gerekir.<\/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 11 dk okuma<\/span><\/p>\n<ol style=\"margin:10px 0 0;padding-left:22px\">\n<li><a href=\"#cdn-nedir-ve-istekleri-nasil-karsilar\">CDN nedir ve istekleri nas\u0131l kar\u015f\u0131lar?<\/a><\/li>\n<li><a href=\"#cdn-web-sitesini-nasil-hizlandirir\">CDN web sitesini nas\u0131l h\u0131zland\u0131r\u0131r?<\/a><\/li>\n<li><a href=\"#cdn-ile-origin-sunucu-arasindaki-fark-nedir\">CDN ile origin sunucu aras\u0131ndaki fark nedir?<\/a><\/li>\n<li><a href=\"#cdn-hangi-icerikleri-cache-eder\">CDN hangi i\u00e7erikleri cache eder?<\/a><\/li>\n<li><a href=\"#cdn-kurulumu-icin-dns-ve-https-nasil-ayarlanir\">CDN kurulumu i\u00e7in DNS ve HTTPS nas\u0131l ayarlan\u0131r?<\/a><\/li>\n<li><a href=\"#cdn-kullanmanin-guvenlik-ve-performans-sinirlari-nelerdir\">CDN kullanman\u0131n g\u00fcvenlik ve performans s\u0131n\u0131rlar\u0131 nelerdir?<\/a><\/li>\n<li><a href=\"#cdn-cache-temizleme-ve-icerik-guncelleme-nasil-yapilir\">CDN cache temizleme ve i\u00e7erik g\u00fcncelleme nas\u0131l yap\u0131l\u0131r?<\/a><\/li>\n<li><a href=\"#cdn-secerken-hangi-olcumleri-izlemelisiniz\">CDN se\u00e7erken hangi \u00f6l\u00e7\u00fcmleri izlemelisiniz?<\/a><\/li>\n<li><a href=\"#cdni-etkinlestirmeden-once-sunlari-kontrol-edin\">CDN&#039;i Etkinle\u015ftirmeden \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=\"cdn-nedir-ve-istekleri-nasil-karsilar\">CDN nedir ve istekleri nas\u0131l kar\u015f\u0131lar?<\/h2>\n<p>Bir web sitesinin t\u00fcm dosyalar\u0131n\u0131 yaln\u0131zca tek bir sunucudan da\u011f\u0131tmak, ziyaret\u00e7i ile sunucu aras\u0131ndaki mesafe artt\u0131k\u00e7a gecikmeyi b\u00fcy\u00fct\u00fcr. CDN, statik i\u00e7erikleri farkl\u0131 b\u00f6lgelerdeki kenar sunucularda \u00f6nbelle\u011fe al\u0131r; ziyaret\u00e7inin DNS y\u00f6nlendirmesiyle kendisine daha yak\u0131n bir noktadan dosya almas\u0131n\u0131 sa\u011flar. B\u00f6ylece origin sunucunun ba\u011flant\u0131 ve i\u015flem y\u00fck\u00fc azal\u0131r.<\/p>\n<p>CDN a\u00e7\u0131l\u0131m\u0131 <em>Content Delivery Network<\/em>, yani \u0130\u00e7erik Da\u011f\u0131t\u0131m A\u011f\u0131d\u0131r. CDN sa\u011flay\u0131c\u0131s\u0131; JavaScript, CSS, g\u00f6rsel, font ve baz\u0131 durumlarda HTML yan\u0131tlar\u0131n\u0131 \u00f6nceden belirlenmi\u015f kurallara g\u00f6re saklar. \u0130stek geldi\u011finde dosya kenar sunucuda varsa do\u011frudan oradan d\u00f6ner. Dosya yoksa CDN, origin ad\u0131 verilen as\u0131l web sunucusundan i\u00e7eri\u011fi al\u0131r, yan\u0131t\u0131 ziyaret\u00e7iye iletir ve uygun g\u00f6r\u00fcl\u00fcrse sonraki istekler i\u00e7in saklar.<\/p>\n<p>Bu mimaride VPS ortadan kalkmaz. VPS \u00e7o\u011fu zaman uygulaman\u0131n, veritaban\u0131n\u0131n ve de\u011fi\u015fken i\u00e7eri\u011fin \u00e7al\u0131\u015ft\u0131\u011f\u0131 origin sunucudur; CDN ise ziyaret\u00e7iye daha yak\u0131n da\u011f\u0131t\u0131m katman\u0131d\u0131r.<\/p>\n<p><strong>CDN&#8217;i statik i\u00e7erik ve kontroll\u00fc \u00f6nbellekleme i\u00e7in konumland\u0131r\u0131n<\/strong> &#8211; oturum, sepet ve y\u00f6netim paneli gibi ki\u015fisel yan\u0131tlar\u0131 varsay\u0131lan olarak cache etmeyin.<\/p>\n<h2 id=\"cdn-web-sitesini-nasil-hizlandirir\">CDN web sitesini nas\u0131l h\u0131zland\u0131r\u0131r?<\/h2>\n<p>H\u0131zlanma tek bir mekanizmadan gelmez. A\u011f mesafesi, TLS ba\u011flant\u0131s\u0131, dosyan\u0131n tekrar indirilmemesi ve origin sunucunun daha az istek i\u015flemesi birlikte etki eder.<\/p>\n<h3>Mesafeyi ve ilk bayt bekleme s\u00fcresini azalt\u0131r<\/h3>\n<p>Ziyaret\u00e7i \u0130zmir&#8217;de, origin sunucu Frankfurt&#8217;ta olabilir. DNS \u00e7\u00f6z\u00fcm\u00fcnden sonra trafik, sa\u011flay\u0131c\u0131n\u0131n uygun g\u00f6rd\u00fc\u011f\u00fc edge noktas\u0131na gider. CDN yan\u0131t\u0131 \u00f6nbellekte tutuyorsa Frankfurt&#8217;a her istekte yeni ba\u011flant\u0131 a\u00e7\u0131lmas\u0131 gerekmez. Bu durum \u00f6zellikle b\u00fcy\u00fck g\u00f6rseller, JavaScript paketleri ve font dosyalar\u0131nda belirgindir.<\/p>\n<p>TTFB, yani ilk bayta kadar ge\u00e7en s\u00fcre, yaln\u0131zca sunucunun PHP veya veritaban\u0131 h\u0131z\u0131n\u0131 \u00f6l\u00e7mez; a\u011f yolunu, TLS anla\u015fmas\u0131n\u0131, edge i\u015flemlerini ve cache durumunu da kapsar. CDN cache hit oldu\u011funda origin uygulamas\u0131na ula\u015f\u0131lmad\u0131\u011f\u0131 i\u00e7in de\u011fi\u015fken uygulama s\u00fcresi devreden \u00e7\u0131kar. Cache miss durumunda ise CDN&#8217;in origin&#8217;e yapt\u0131\u011f\u0131 iste\u011fin s\u00fcresi yine hesaba kat\u0131l\u0131r.<\/p>\n<h3>Tekrar indirmeleri \u00f6nler<\/h3>\n<p>Taray\u0131c\u0131 \u00f6nbelle\u011fi ile CDN \u00f6nbelle\u011fi ayn\u0131 \u015fey de\u011fildir. Taray\u0131c\u0131 dosyay\u0131 kullan\u0131c\u0131n\u0131n cihaz\u0131nda saklar; CDN ise ayn\u0131 i\u00e7eri\u011fi birden fazla ziyaret\u00e7i i\u00e7in edge noktas\u0131nda saklar. HTTP <code>Cache-Control<\/code> ba\u015fl\u0131\u011f\u0131ndaki <code>max-age<\/code>, <code>s-maxage<\/code> ve <code>no-store<\/code> y\u00f6nergeleri bu katmanlar\u0131n davran\u0131\u015f\u0131n\u0131 etkiler. RFC 9111, HTTP \u00f6nbelleklerinin temel kurallar\u0131n\u0131 tan\u0131mlar.<\/p>\n<p>\u00d6rne\u011fin, s\u00fcr\u00fcmlenmi\u015f bir CSS dosyas\u0131 i\u00e7in <code>Cache-Control: public, max-age=31536000, immutable<\/code> kullan\u0131labilir. Buradaki 31536000 saniye 365 g\u00fcne kar\u015f\u0131l\u0131k gelir. Dosya i\u00e7eri\u011fi de\u011fi\u015fti\u011finde ayn\u0131 URL&#8217;yi kullanmak yerine <code>app.2026-09.css<\/code> gibi yeni bir dosya ad\u0131 \u00fcretmek gerekir.<\/p>\n<p><strong>\u00d6nbellek s\u00fcresini i\u00e7erik t\u00fcr\u00fcne g\u00f6re belirleyin<\/strong> &#8211; s\u00fcr\u00fcmlenmi\u015f statik dosyalarda uzun, s\u0131k de\u011fi\u015fen HTML yan\u0131tlar\u0131nda k\u0131sa TTL kullan\u0131n.<\/p>\n<h2 id=\"cdn-ile-origin-sunucu-arasindaki-fark-nedir\">CDN ile origin sunucu aras\u0131ndaki fark nedir?<\/h2>\n<table>\n<thead>\n<tr>\n<th>Katman<\/th>\n<th>Temel g\u00f6rev<\/th>\n<th>Tipik i\u00e7erik<\/th>\n<th>Ar\u0131za etkisi<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Origin sunucu<\/td>\n<td>Uygulamay\u0131 \u00e7al\u0131\u015ft\u0131r\u0131r ve as\u0131l yan\u0131t\u0131 \u00fcretir<\/td>\n<td>PHP, Node.js, veritaban\u0131, ki\u015fiselle\u015ftirilmi\u015f HTML<\/td>\n<td>Uygulama ve dinamik istekler do\u011frudan etkilenir<\/td>\n<\/tr>\n<tr>\n<td>CDN edge<\/td>\n<td>\u0130\u00e7eri\u011fi ziyaret\u00e7iye yak\u0131n noktadan sunar<\/td>\n<td>CSS, JavaScript, g\u00f6rsel, font, cache&#8217;lenmi\u015f yan\u0131t<\/td>\n<td>Cache hit i\u00e7erik bir s\u00fcre sunulabilir<\/td>\n<\/tr>\n<tr>\n<td>Taray\u0131c\u0131 \u00f6nbelle\u011fi<\/td>\n<td>Dosyay\u0131 kullan\u0131c\u0131 cihaz\u0131nda saklar<\/td>\n<td>Daha \u00f6nce indirilmi\u015f HTTP kaynaklar\u0131<\/td>\n<td>Yaln\u0131zca o istemcinin tekrar indirmesi azal\u0131r<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Origin, uygulaman\u0131n do\u011fruluk kayna\u011f\u0131d\u0131r. Kullan\u0131c\u0131 hesab\u0131, sepet, sipari\u015f veya y\u00f6netim i\u015flemleri gibi yan\u0131tlar \u00e7o\u011funlukla burada \u00fcretilir. CDN ise da\u011f\u0131t\u0131m ve trafik emme katman\u0131 olarak davran\u0131r. Her dosyay\u0131 k\u00f6rlemesine cache etmek do\u011fru de\u011fildir; yanl\u0131\u015f bir kural, bir kullan\u0131c\u0131n\u0131n HTML yan\u0131t\u0131n\u0131 ba\u015fka bir kullan\u0131c\u0131ya g\u00f6sterebilir.<\/p>\n<p>CDN kullan\u0131rken origin sunucunun yaln\u0131zca CDN IP aral\u0131klar\u0131ndan gelen HTTP ve HTTPS trafi\u011fini kabul etmesi s\u0131k kullan\u0131lan bir g\u00fcvenlik modelidir. Sa\u011flay\u0131c\u0131n\u0131n g\u00fcncel IP listesi otomatik veya d\u00fczenli bi\u00e7imde takip edilmelidir. Sabit bir listeyi y\u0131llarca de\u011fi\u015ftirmemek, CDN&#8217;in yeni edge noktalar\u0131n\u0131 fark\u0131nda olmadan engelleyebilir.<\/p>\n<p>Origin \u00fczerinde Nginx \u00e7al\u0131\u015f\u0131yorsa temel proxy ba\u015fl\u0131klar\u0131, ger\u00e7ek istemci IP&#8217;si ve HTTPS durumu ayr\u0131ca ele al\u0131nmal\u0131d\u0131r. Reverse proxy katman\u0131n\u0131 yeni kuruyorsan\u0131z <a href=\"https:\/\/www.vps.tc\/blog\/tr\/ubuntu-nginx-kurulumu-ilk-yapilandirma\/\">Ubuntu&#8217;da Nginx Kurulumu ve \u0130lk Yap\u0131land\u0131rma Rehberi<\/a> i\u00e7indeki temel sanal host ad\u0131mlar\u0131 yard\u0131mc\u0131 olabilir.<\/p>\n<h2 id=\"cdn-hangi-icerikleri-cache-eder\">CDN hangi i\u00e7erikleri cache eder?<\/h2>\n<p>En g\u00fcvenli ba\u015flang\u0131\u00e7, de\u011fi\u015fmeyen ve URL&#8217;si i\u00e7erik s\u00fcr\u00fcm\u00fcn\u00fc ta\u015f\u0131yan dosyalard\u0131r. A\u015fa\u011f\u0131daki i\u00e7erikler \u00e7o\u011fu sitede CDN i\u00e7in uygundur:<\/p>\n<ul>\n<li>CSS ve JavaScript dosyalar\u0131<\/li>\n<li>JPEG, PNG, WebP, AVIF ve SVG g\u00f6rselleri<\/li>\n<li>Web fontlar\u0131<\/li>\n<li>Video par\u00e7alar\u0131 ve indirilebilir statik dosyalar<\/li>\n<li>Versiyonlanm\u0131\u015f API yan\u0131tlar\u0131<\/li>\n<\/ul>\n<p>HTML i\u00e7in karar daha dikkatli verilmelidir. Bir blogun herkese ayn\u0131 g\u00f6r\u00fcnen yaz\u0131 sayfas\u0131 cache edilebilir; ancak kullan\u0131c\u0131 ad\u0131, sepet, para birimi veya oturum durumu yan\u0131t\u0131 de\u011fi\u015ftiriyorsa <code>private<\/code> ya da <code>no-store<\/code> tercih edilmelidir.<\/p>\n<p>Cookie kullan\u0131m\u0131 da \u00f6nemlidir. Baz\u0131 CDN kurallar\u0131 <code>Cookie<\/code> ba\u015fl\u0131\u011f\u0131 ta\u015f\u0131yan yan\u0131tlar\u0131 varsay\u0131lan olarak cache d\u0131\u015f\u0131 b\u0131rak\u0131r. Baz\u0131 kurulumlarda ise yaln\u0131zca belirli cookie&#8217;ler hesaba kat\u0131l\u0131r. Cache anahtar\u0131na gereksiz sorgu parametreleri eklenmesi de hit oran\u0131n\u0131 d\u00fc\u015f\u00fcr\u00fcr. <code>?utm_source=<\/code> gibi analitik parametreler i\u00e7in normalle\u015ftirme yap\u0131labiliyorsa ayn\u0131 i\u00e7eri\u011fin onlarca ayr\u0131 kopyas\u0131 olu\u015fmaz.<\/p>\n<h3>Cache-Control ba\u015fl\u0131klar\u0131n\u0131 kontrol etme<\/h3>\n<p>\u00dcretim sitenizde CDN eklemeden \u00f6nce origin yan\u0131t\u0131n\u0131 inceleyin:<\/p>\n<pre><code>curl -I https:\/\/www.example.com\/assets\/app.2026-09.css<\/code><\/pre>\n<p>\u00c7\u0131kt\u0131da <code>Cache-Control<\/code>, <code>ETag<\/code>, <code>Last-Modified<\/code> ve varsa CDN&#8217;e ait <code>Age<\/code>, <code>X-Cache<\/code> veya benzeri ba\u015fl\u0131klar incelenir. Sa\u011flay\u0131c\u0131lar bu ba\u015fl\u0131klar\u0131 farkl\u0131 adlarla g\u00f6sterebilir; tek bir header ad\u0131na g\u00fcvenmek yerine paneldeki cache durumuyla kar\u015f\u0131la\u015ft\u0131r\u0131n.<\/p>\n<p>CDN&#8217;in ayn\u0131 dosyaya ikinci istekte cache hit \u00fcretip \u00fcretmedi\u011fini g\u00f6rmek i\u00e7in birka\u00e7 saniye arayla yeniden istek g\u00f6nderilebilir:<\/p>\n<pre><code>curl -sS -D - -o \/dev\/null https:\/\/www.example.com\/assets\/app.2026-09.css<\/code><\/pre>\n<p><code>-D -<\/code> yan\u0131t ba\u015fl\u0131klar\u0131n\u0131 ekrana basar, <code>-o \/dev\/null<\/code> ise dosyan\u0131n g\u00f6vdesini indirmeden testi tamamlar. \u0130lk iste\u011fin cache miss, sonraki iste\u011fin hit olmas\u0131 beklenir; ancak edge noktas\u0131, TTL ve sa\u011flay\u0131c\u0131 politikas\u0131na g\u00f6re sonu\u00e7 de\u011fi\u015febilir.<\/p>\n<p><strong>Cache hit durumunu ba\u015fl\u0131klarla do\u011frulay\u0131n<\/strong> &#8211; yaln\u0131zca h\u0131z testi skoruna bakarak CDN&#8217;in do\u011fru \u00e7al\u0131\u015ft\u0131\u011f\u0131n\u0131 varsaymay\u0131n.<\/p>\n<div class=\"aiw-callout aiw-callout-tip\">\n<p class=\"aiw-callout-label\">\u0130pucu<\/p>\n<p>\u0130lk testte t\u00fcm siteyi CDN&#039;e almay\u0131n. \u00d6nce s\u00fcr\u00fcmlenmi\u015f CSS, JavaScript ve g\u00f6rsel dizinini se\u00e7in; curl ile Cache-Control ve cache durumunu do\u011frulad\u0131ktan sonra kapsam\u0131 geni\u015fletin.<\/p>\n<\/div>\n<h2 id=\"cdn-kurulumu-icin-dns-ve-https-nasil-ayarlanir\">CDN kurulumu i\u00e7in DNS ve HTTPS nas\u0131l ayarlan\u0131r?<\/h2>\n<p>CDN kurulumu genellikle alan ad\u0131n\u0131n DNS kay\u0131tlar\u0131n\u0131 sa\u011flay\u0131c\u0131n\u0131n a\u011f\u0131na y\u00f6nlendirmekle ba\u015flar. Yayg\u0131n modelde <code>www.example.com<\/code> i\u00e7in bir CNAME kayd\u0131, k\u00f6k alan ad\u0131 i\u00e7in ise sa\u011flay\u0131c\u0131n\u0131n destekledi\u011fi ALIAS, ANAME veya apex y\u00f6nlendirme y\u00f6ntemi kullan\u0131l\u0131r. DNS&#8217;te CNAME bir alan ad\u0131n\u0131 ba\u015fka bir alan ad\u0131na ba\u011flar; do\u011frudan IP adresi vermez.<\/p>\n<p>De\u011fi\u015fiklikten \u00f6nce mevcut kay\u0131tlar\u0131 not edin. <code>MX<\/code> kay\u0131tlar\u0131 e-posta trafi\u011fini, <code>TXT<\/code> kay\u0131tlar\u0131 do\u011frulama ve SPF yap\u0131land\u0131rmas\u0131n\u0131, <code>CAA<\/code> kay\u0131tlar\u0131 ise sertifika yetkilendirmesini etkileyebilir. Yaln\u0131zca web kayd\u0131n\u0131 ta\u015f\u0131y\u0131p e-posta kay\u0131tlar\u0131n\u0131 yanl\u0131\u015fl\u0131kla silmek s\u0131k rastlanan bir ge\u00e7i\u015f hatas\u0131d\u0131r.<\/p>\n<pre><code>dig +short www.example.com CNAME\ndig +short www.example.com A\ndig +short example.com MX<\/code><\/pre>\n<p>\u0130lk komut CNAME hedefini, ikinci komut IPv4 yan\u0131t\u0131n\u0131, \u00fc\u00e7\u00fcnc\u00fc komut posta sunucular\u0131n\u0131 g\u00f6sterir. DNS yan\u0131t\u0131 tek bir makinede hemen de\u011fi\u015fmeyebilir; TTL, resolver \u00f6nbelle\u011fi ve sa\u011flay\u0131c\u0131n\u0131n da\u011f\u0131t\u0131m s\u00fcresi birlikte de\u011ferlendirilmelidir. DNS te\u015fhisinde panelden \u00f6nce <code>dig +short<\/code> kullanmak, g\u00f6r\u00fcnen kay\u0131t ile ger\u00e7ekten d\u00f6nen kay\u0131t aras\u0131ndaki fark\u0131 h\u0131zl\u0131ca ortaya \u00e7\u0131kar\u0131r.<\/p>\n<p>HTTPS taraf\u0131nda sertifika CDN edge noktalar\u0131nda sunulur. Origin ile CDN aras\u0131ndaki ba\u011flant\u0131 da m\u00fcmk\u00fcnse HTTPS olmal\u0131 ve sertifika do\u011frulamas\u0131 kapat\u0131lmamal\u0131d\u0131r. &#8220;Flexible&#8221; benzeri modeller, ziyaret\u00e7i ile CDN aras\u0131n\u0131 \u015fifreleyip CDN ile origin aras\u0131n\u0131 d\u00fcz HTTP b\u0131rakabilir; bu yakla\u015f\u0131m oturum cookie&#8217;leri ve giri\u015f bilgileri i\u00e7in uygun de\u011fildir.<\/p>\n<p>CDN, origin&#8217;e hangi Host ba\u015fl\u0131\u011f\u0131n\u0131 g\u00f6nderece\u011fini ve SNI de\u011ferini do\u011fru kullanmal\u0131d\u0131r. Origin sertifikas\u0131 yaln\u0131zca i\u00e7 a\u011f ad\u0131n\u0131 kaps\u0131yorsa do\u011frulama hatas\u0131 olu\u015fabilir. Sertifika yenileme, y\u00f6nlendirme ve HTTP-HTTPS politikas\u0131 ge\u00e7i\u015ften \u00f6nce test edilmelidir.<\/p>\n<div class=\"aiw-callout aiw-callout-field\">\n<p class=\"aiw-callout-label\">Sahadan not<\/p>\n<p>Bir CDN ge\u00e7i\u015finde IPv4 kayd\u0131n\u0131 ta\u015f\u0131d\u0131ktan sonra eski origin&#039;i g\u00f6steren AAAA kayd\u0131n\u0131 fark ettim. curl -4 ba\u015far\u0131l\u0131yken curl -6 iste\u011fi 502 d\u00f6n\u00fcyordu; dig ile AAAA kayd\u0131n\u0131 do\u011frulay\u0131p d\u00fczelttikten sonra iki protokolde de ayn\u0131 edge ak\u0131\u015f\u0131n\u0131 g\u00f6rd\u00fcm.<\/p>\n<\/div>\n<h2 id=\"cdn-kullanmanin-guvenlik-ve-performans-sinirlari-nelerdir\">CDN kullanman\u0131n g\u00fcvenlik ve performans s\u0131n\u0131rlar\u0131 nelerdir?<\/h2>\n<p>CDN, DDoS trafi\u011finin tamam\u0131n\u0131 sihirli bi\u00e7imde yok etmez. Sa\u011flay\u0131c\u0131n\u0131n kapasitesi, koruma katmanlar\u0131, rate limit kurallar\u0131 ve uygulamaya \u00f6zg\u00fc sald\u0131r\u0131lar\u0131n niteli\u011fi \u00f6nemlidir. \u00d6zellikle ge\u00e7ersiz parametrelerle cache bypass yapan istekler origin&#8217;e kadar ula\u015fabilir.<\/p>\n<p>Origin IP adresi daha \u00f6nce DNS kay\u0131tlar\u0131nda, e-posta ba\u015fl\u0131klar\u0131nda, eski bir alt alan ad\u0131nda veya do\u011frudan sunucu banner&#8217;lar\u0131nda a\u00e7\u0131\u011fa \u00e7\u0131km\u0131\u015fsa sald\u0131rgan CDN&#8217;i atlayabilir. Origin firewall&#8217;\u0131 yaln\u0131zca CDN&#8217;in kaynak a\u011flar\u0131na izin verecek \u015fekilde daraltmak bu riski azalt\u0131r. SSH i\u00e7in 22 numaral\u0131 portu de\u011fi\u015ftirmek tek ba\u015f\u0131na g\u00fcvenlik de\u011fildir; y\u00f6netim eri\u015fimi anahtar tabanl\u0131 kimlik do\u011frulama, firewall ve izleme ile korunmal\u0131d\u0131r.<\/p>\n<p>Rate limit kural\u0131n\u0131 \u00f6nce g\u00f6zlem modunda uygulamak daha g\u00fcvenlidir. Giri\u015f endpoint&#8217;ine IP ba\u015f\u0131na \u00e7ok d\u00fc\u015f\u00fck bir s\u0131n\u0131r koymak, ortak NAT kullanan ger\u00e7ek kullan\u0131c\u0131lar\u0131 da engelleyebilir. API istemcileri i\u00e7in kimlik, token veya kullan\u0131c\u0131 hesab\u0131 temelli s\u0131n\u0131rlar IP tabanl\u0131 kurallardan daha uygun olabilir.<\/p>\n<p>Bir CDN, veritaban\u0131 sorgular\u0131n\u0131 h\u0131zland\u0131rmaz. Uygulama her cache miss&#8217;te pahal\u0131 sorgu \u00e7al\u0131\u015ft\u0131r\u0131yorsa origin h\u00e2l\u00e2 yava\u015f kal\u0131r. Sorgu taraf\u0131ndaki darbo\u011fazlar i\u00e7in <a href=\"https:\/\/www.vps.tc\/blog\/tr\/veritabani-indeksi-nedir-sorgular-nasil-hizlanir\/\">Veritaban\u0131 \u0130ndeksi Nedir? Sorgular Nas\u0131l H\u0131zlan\u0131r?<\/a> yaz\u0131s\u0131ndaki <code>EXPLAIN<\/code> yakla\u015f\u0131m\u0131 ayr\u0131 bir \u00e7al\u0131\u015fma alan\u0131d\u0131r. CDN, veritaban\u0131 optimizasyonunun yerine ge\u00e7mez.<\/p>\n<p>Benzer \u015fekilde CDN, origin&#8217;deki 502 hatas\u0131n\u0131 ortadan kald\u0131rmaz. Nginx ile PHP-FPM, upstream veya uygulama aras\u0131ndaki kopukluk devam eder; yaln\u0131zca daha \u00f6nce cache&#8217;lenmi\u015f baz\u0131 yan\u0131tlar eri\u015filebilir kalabilir. <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> i\u00e7indeki upstream ve log kontrolleri bu noktada h\u00e2l\u00e2 ge\u00e7erlidir.<\/p>\n<p><strong>Origin&#8217;i do\u011frudan eri\u015fime a\u00e7\u0131k b\u0131rakmay\u0131n<\/strong> &#8211; CDN devredeyken bile firewall, uygulama loglar\u0131 ve kaynak IP do\u011frulamas\u0131n\u0131 birlikte izleyin.<\/p>\n<div class=\"aiw-callout aiw-callout-warn\">\n<p class=\"aiw-callout-label\">Dikkat<\/p>\n<p>CDN arkas\u0131ndaki origin IP&#039;si do\u011frudan eri\u015filebilir kal\u0131rsa sald\u0131rgan CDN kurallar\u0131n\u0131 atlayabilir. Firewall kaynaklar\u0131n\u0131 sa\u011flay\u0131c\u0131n\u0131n g\u00fcncel a\u011flar\u0131yla s\u0131n\u0131rland\u0131r\u0131n ve origin \u00fczerinde beklenmeyen Host ba\u015fl\u0131klar\u0131n\u0131 reddedin.<\/p>\n<\/div>\n<h2 id=\"cdn-cache-temizleme-ve-icerik-guncelleme-nasil-yapilir\">CDN cache temizleme ve i\u00e7erik g\u00fcncelleme nas\u0131l yap\u0131l\u0131r?<\/h2>\n<p>Cache temizleme, CDN&#8217;de saklanan nesnelerin silinip sonraki istekte origin&#8217;den yeniden al\u0131nmas\u0131d\u0131r. T\u00fcm cache&#8217;i temizlemek kolay g\u00f6r\u00fcn\u00fcr; ancak y\u00fcksek trafikli bir sitede ayn\u0131 anda \u00e7ok say\u0131da iste\u011fin origin&#8217;e d\u00f6nmesine neden olabilir. Buna cache stampede veya thundering herd etkisi denir.<\/p>\n<p>Tercih edilen y\u00f6ntem, dosyalar\u0131 s\u00fcr\u00fcmlemektir. <code>style.css<\/code> yerine <code>style.2026-09-25.css<\/code> kullan\u0131l\u0131r ve HTML yeni dosya ad\u0131na ge\u00e7irilir. Acil bir d\u00fczeltmede yaln\u0131zca ilgili URL i\u00e7in purge uygulan\u0131r. HTML ve API yan\u0131tlar\u0131nda k\u0131sa TTL, stale-while-revalidate veya sa\u011flay\u0131c\u0131n\u0131n benzeri mekanizmalar\u0131 kontroll\u00fc bi\u00e7imde kullan\u0131labilir.<\/p>\n<p>Cache temizleme sonras\u0131nda \u00fc\u00e7 kontrol yap\u0131lmal\u0131d\u0131r:<\/p>\n<ol>\n<li>Yeni i\u00e7eri\u011fin origin yan\u0131t\u0131nda bulundu\u011funu do\u011frulay\u0131n.<\/li>\n<li>Farkl\u0131 bir edge noktas\u0131ndan cache durumunu kontrol edin.<\/li>\n<li>Taray\u0131c\u0131 \u00f6nbelle\u011finin eski dosyay\u0131 kullanmad\u0131\u011f\u0131ndan emin olun.<\/li>\n<\/ol>\n<p>301 y\u00f6nlendirmeleri de cache&#8217;lenebilir. Yanl\u0131\u015f bir kal\u0131c\u0131 y\u00f6nlendirme uzun s\u00fcre istemcilerde ve CDN noktalar\u0131nda kalabilir. Alan ad\u0131 veya HTTPS ge\u00e7i\u015fi planlan\u0131yorsa <a href=\"https:\/\/www.vps.tc\/blog\/tr\/301-yonlendirme-nedir-seo-kullanim-rehberi\/\">301 Y\u00f6nlendirme Nedir? SEO \u0130\u00e7in Kullan\u0131m Rehberi<\/a> i\u00e7indeki ge\u00e7i\u015f s\u0131ras\u0131n\u0131 izlemek, geri d\u00f6n\u00fc\u015f plan\u0131 haz\u0131rlamadan kal\u0131c\u0131 y\u00f6nlendirme yay\u0131mlamaktan daha g\u00fcvenlidir.<\/p>\n<div class=\"aiw-callout aiw-callout-example\">\n<p class=\"aiw-callout-label\">\u00d6rnek<\/p>\n<p>Bir \u00fcr\u00fcn g\u00f6rseli g\u00fcncellendi\u011finde ayn\u0131 dosya ad\u0131n\u0131 korumak eski i\u00e7eri\u011fin CDN&#039;de kalmas\u0131na yol a\u00e7abilir. Dosya ad\u0131n\u0131 veya sorgu s\u00fcr\u00fcm\u00fcn\u00fc de\u011fi\u015ftirip yaln\u0131zca ilgili URL&#039;yi temizlemek, t\u00fcm cache&#039;i bo\u015faltmaktan daha kontroll\u00fc bir senaryodur.<\/p>\n<\/div>\n<h2 id=\"cdn-secerken-hangi-olcumleri-izlemelisiniz\">CDN se\u00e7erken hangi \u00f6l\u00e7\u00fcmleri izlemelisiniz?<\/h2>\n<p>&#8220;CDN aktif&#8221; bilgisi tek ba\u015f\u0131na yeterli de\u011fildir. \u0130zleme panelinde en az cache hit oran\u0131, origin istek say\u0131s\u0131, origin yan\u0131t s\u00fcresi, HTTP durum kodlar\u0131, bant geni\u015fli\u011fi ve edge b\u00f6lgesi baz\u0131nda gecikme takip edilmelidir.<\/p>\n<p>Cache hit oran\u0131 y\u00fckselirken kullan\u0131c\u0131 deneyimi k\u00f6t\u00fcle\u015febilir; \u00f6rne\u011fin CDN eski HTML&#8217;i h\u0131zl\u0131ca sunuyor olabilir. Bu nedenle \u00f6l\u00e7\u00fcmler URL t\u00fcr\u00fcne g\u00f6re ayr\u0131lmal\u0131d\u0131r. Statik dosyalarda y\u00fcksek hit beklenirken ki\u015fiselle\u015ftirilmi\u015f endpoint&#8217;lerde d\u00fc\u015f\u00fck veya s\u0131f\u0131r hit normal olabilir.<\/p>\n<p>Ger\u00e7ek kullan\u0131c\u0131 \u00f6l\u00e7\u00fcmleri ile sentetik testleri ay\u0131r\u0131n. Lighthouse ve benzeri ara\u00e7lar tek bir lokasyondan test yapabilir. Farkl\u0131 b\u00f6lgelerden <code>curl<\/code> testleri, RUM verileri ve uygulama loglar\u0131 birlikte de\u011ferlendirilmelidir. HTTP\/2 ve HTTP\/3 deste\u011fi de \u00f6l\u00e7\u00fclmelidir; QUIC hakk\u0131nda temel bilgi i\u00e7in <a href=\"https:\/\/www.vps.tc\/blog\/tr\/quic-nedir-http3-ve-tcp-farklari\/\">QUIC Nedir? Daha H\u0131zl\u0131 \u0130nternet Protokol\u00fc<\/a> ba\u015fl\u0131\u011f\u0131na bakabilirsiniz.<\/p>\n<p>\u00d6rnek bir kontrol d\u00f6ng\u00fcs\u00fc \u015f\u00f6yledir: \u00f6nce CDN \u00f6ncesi TTFB ve origin CPU de\u011ferlerini kaydedin, sonra yaln\u0131zca statik dosyalar\u0131 CDN&#8217;e al\u0131n, hit oran\u0131n\u0131 ve hata kodlar\u0131n\u0131 izleyin, en son HTML cache kurallar\u0131n\u0131 k\u00fc\u00e7\u00fck bir URL grubunda deneyin. Her a\u015famada geri alma yolu bulunmal\u0131d\u0131r.<\/p>\n<p>Bir sayfan\u0131n h\u0131zlanmamas\u0131 CDN&#8217;in ba\u015far\u0131s\u0131z oldu\u011fu anlam\u0131na gelmez. HTML yan\u0131t\u0131 dinamik olabilir, g\u00f6rseller gere\u011finden b\u00fcy\u00fck olabilir, JavaScript ana i\u015f par\u00e7ac\u0131\u011f\u0131n\u0131 uzun s\u00fcre me\u015fgul edebilir veya origin sorgular\u0131 yava\u015f olabilir. CDN a\u011f transferini ve tekrar indirmeleri azalt\u0131r; taray\u0131c\u0131 render maliyetini tek ba\u015f\u0131na \u00e7\u00f6zmez.<\/p>\n<h2 id=\"cdni-etkinlestirmeden-once-sunlari-kontrol-edin\">CDN&#039;i Etkinle\u015ftirmeden \u00d6nce \u015eunlar\u0131 Kontrol Edin<\/h2>\n<ul class=\"aiw-checklist\">\n<li>Statik ve dinamik i\u00e7erik URL&#039;lerini ay\u0131r\u0131n.<\/li>\n<li>CSS, JavaScript ve g\u00f6rseller i\u00e7in Cache-Control ba\u015fl\u0131klar\u0131n\u0131 belirleyin.<\/li>\n<li>Origin sunucunun ger\u00e7ek IP adresini do\u011frudan eri\u015fime kar\u015f\u0131 s\u0131n\u0131rland\u0131r\u0131n.<\/li>\n<li>DNS kay\u0131tlar\u0131n\u0131 ve mevcut MX, TXT, CAA de\u011ferlerini yedekleyin.<\/li>\n<li>CDN ile origin aras\u0131ndaki HTTPS sertifika do\u011frulamas\u0131n\u0131 test edin.<\/li>\n<li>Cache hit, origin gecikmesi ve HTTP hata kodlar\u0131 i\u00e7in izleme kurun.<\/li>\n<li>Tek URL purge ve geri d\u00f6n\u00fc\u015f prosed\u00fcr\u00fcn\u00fc ger\u00e7ek bir dosyayla deneyin.<\/li>\n<\/ul>\n<div class=\"aiw-cta\">\n<p>\u0130lk denemede yaln\u0131zca s\u00fcr\u00fcmlenmi\u015f statik dosyalar\u0131 CDN arkas\u0131na al\u0131p cache ba\u015fl\u0131klar\u0131n\u0131 ve origin y\u00fck\u00fcn\u00fc \u00f6l\u00e7ebilirsiniz. Test temiz ge\u00e7erse HTML ve API kurallar\u0131n\u0131 k\u00fc\u00e7\u00fck bir URL grubunda deneyin.<\/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>CDN kullanmak web sitesini kesin olarak h\u0131zland\u0131r\u0131r m\u0131?<\/summary>\n<p>Hay\u0131r. CDN, \u00f6zellikle statik dosyalarda a\u011f mesafesini ve tekrar indirmeleri azalt\u0131r; ancak dinamik PHP kodu, veritaban\u0131 sorgular\u0131, b\u00fcy\u00fck g\u00f6rseller veya taray\u0131c\u0131daki JavaScript i\u015flemleri yava\u015fsa bunlar\u0131 kendili\u011finden \u00e7\u00f6zmez. H\u0131z kazan\u0131m\u0131n\u0131 g\u00f6rmek i\u00e7in CDN \u00f6ncesi ve sonras\u0131 TTFB, dosya indirme s\u00fcresi, cache hit oran\u0131 ve origin yan\u0131t s\u00fcresini birlikte \u00f6l\u00e7\u00fcn.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>CDN \u00fccretsiz kullan\u0131labilir mi?<\/summary>\n<p>Baz\u0131 sa\u011flay\u0131c\u0131lar s\u0131n\u0131rl\u0131 trafik, \u00f6zellik ve alan ad\u0131 kapsam\u0131yla \u00fccretsiz plan sunar; ancak fiyatland\u0131rma sa\u011flay\u0131c\u0131ya, b\u00f6lgeye, istek say\u0131s\u0131na ve veri transferine g\u00f6re de\u011fi\u015fir. \u00dccretsiz plan\u0131n DDoS korumas\u0131, log saklama s\u00fcresi, purge API&#039;si ve HTTPS \u00f6zelliklerini ayr\u0131ca inceleyin. Y\u00fcksek trafikte yaln\u0131zca ayl\u0131k \u00fccret de\u011fil, origin \u00e7\u0131k\u0131\u015f trafi\u011fi ve ek g\u00fcvenlik hizmetleri de hesaba kat\u0131lmal\u0131d\u0131r.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>CDN WordPress i\u00e7in gerekli midir?<\/summary>\n<p>Her WordPress sitesi i\u00e7in zorunlu de\u011fildir. Ziyaret\u00e7ileri farkl\u0131 b\u00f6lgelerde bulunan, g\u00f6rsel ve statik dosya trafi\u011fi y\u00fcksek sitelerde fayda sa\u011flayabilir. \u00d6nce sayfa cache politikas\u0131, g\u00f6rsel boyutlar\u0131, PHP \u00e7al\u0131\u015fma s\u00fcresi ve veritaban\u0131 sorgular\u0131 incelenmelidir. Y\u00f6netim paneli, giri\u015f sayfas\u0131, sepet ve kullan\u0131c\u0131ya \u00f6zel yan\u0131tlar CDN cache kapsam\u0131 d\u0131\u015f\u0131nda tutulmal\u0131d\u0131r.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>CDN kullan\u0131rken DNS kay\u0131tlar\u0131 de\u011fi\u015fir mi?<\/summary>\n<p>\u00c7o\u011fu kurulumda web alan ad\u0131n\u0131n A, AAAA veya CNAME davran\u0131\u015f\u0131 CDN&#039;e g\u00f6re de\u011fi\u015ftirilir. MX kay\u0131tlar\u0131 e-posta i\u00e7indir ve web ge\u00e7i\u015fi s\u0131ras\u0131nda korunmal\u0131d\u0131r. TXT kay\u0131tlar\u0131 SPF, do\u011frulama ve \u00e7e\u015fitli g\u00fcvenlik politikalar\u0131 i\u00e7in kullan\u0131labilir. De\u011fi\u015fiklikten \u00f6nce mevcut zone kayd\u0131n\u0131 d\u0131\u015fa aktar\u0131n; sonras\u0131nda dig ile CNAME, A, AAAA ve MX yan\u0131tlar\u0131n\u0131 ayr\u0131 ayr\u0131 do\u011frulay\u0131n.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>CDN cache nas\u0131l temizlenir?<\/summary>\n<p>Sa\u011flay\u0131c\u0131n\u0131n panelindeki purge veya API \u00f6zelli\u011fi kullan\u0131l\u0131r. En g\u00fcvenli y\u00f6ntem, \u00f6nce yaln\u0131zca de\u011fi\u015fen URL&#039;yi temizlemektir. T\u00fcm cache&#039;i bo\u015faltmak, \u00e7ok say\u0131da iste\u011fin ayn\u0131 anda origin&#039;e d\u00f6nmesine ve ge\u00e7ici y\u00fck art\u0131\u015f\u0131na neden olabilir. Uzun cache s\u00fcreleri kullan\u0131lan statik dosyalarda dosya ad\u0131n\u0131 s\u00fcr\u00fcmleyerek yeni URL yay\u0131mlamak, s\u0131k purge ihtiyac\u0131n\u0131 azalt\u0131r.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>CDN origin sunucuyu gizler mi?<\/summary>\n<p>Tek ba\u015f\u0131na garanti etmez. Origin IP&#039;si eski DNS kay\u0131tlar\u0131nda, do\u011frudan kullan\u0131lan alt alan adlar\u0131nda, e-posta ba\u015fl\u0131klar\u0131nda veya servis banner&#039;lar\u0131nda g\u00f6r\u00fcn\u00fcyorsa bulunabilir. Origin firewall&#039;\u0131 yaln\u0131zca CDN sa\u011flay\u0131c\u0131s\u0131n\u0131n g\u00fcncel kaynak a\u011flar\u0131na izin verecek \u015fekilde yap\u0131land\u0131r\u0131lmal\u0131, y\u00f6netim portlar\u0131 ayr\u0131 eri\u015fim kurallar\u0131yla korunmal\u0131d\u0131r. Uygulama loglar\u0131nda CDN d\u0131\u015f\u0131 do\u011frudan istekleri d\u00fczenli olarak aray\u0131n.<\/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\/rfc9111\" target=\"_blank\" rel=\"noopener\">RFC 9111 &#8211; HTTP Caching<\/a> \u2014 rfc-editor.org<\/li>\n<li><a href=\"https:\/\/developer.mozilla.org\/en-US\/docs\/Web\/HTTP\/Guides\/Caching\" target=\"_blank\" rel=\"noopener\">MDN &#8211; HTTP Caching<\/a> \u2014 developer.mozilla.org<\/li>\n<li><a href=\"https:\/\/developers.cloudflare.com\/cache\/\" target=\"_blank\" rel=\"noopener\">Cloudflare &#8211; Cache Documentation<\/a> \u2014 developers.cloudflare.com<\/li>\n<li><a href=\"https:\/\/nginx.org\/en\/docs\/http\/ngx_http_proxy_module.html\" target=\"_blank\" rel=\"noopener\">nginx &#8211; Proxy Module<\/a> \u2014 nginx.org<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>CDN, web sitesi dosyalar\u0131n\u0131 ziyaret\u00e7iye yak\u0131n edge sunuculardan da\u011f\u0131tarak a\u011f gecikmesini ve origin y\u00fck\u00fcn\u00fc azalt\u0131r. Cache, DNS, HTTPS ve g\u00fcvenlik ayarlar\u0131 a\u00e7\u0131klan\u0131yor.<\/p>\n","protected":false},"author":2,"featured_media":937,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[17],"tags":[],"class_list":["post-939","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-genel"],"lang":"tr","translations":{"tr":939,"en":940},"pll_sync_post":[],"_links":{"self":[{"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/posts\/939","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=939"}],"version-history":[{"count":1,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/posts\/939\/revisions"}],"predecessor-version":[{"id":941,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/posts\/939\/revisions\/941"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/media\/937"}],"wp:attachment":[{"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/media?parent=939"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/categories?post=939"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/tags?post=939"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}