{"id":3574,"date":"2025-12-28T15:42:38","date_gmt":"2025-12-28T12:42:38","guid":{"rendered":"https:\/\/www.dchost.com\/blog\/tarayici-ve-cdn-onbellekleme-neden-bu-kadar-kritik\/"},"modified":"2026-11-04T17:51:49","modified_gmt":"2026-11-04T14:51:49","slug":"tarayici-ve-cdn-onbellekleme-neden-bu-kadar-kritik","status":"publish","type":"post","link":"https:\/\/www.dchost.com\/blog\/tarayici-ve-cdn-onbellekleme-neden-bu-kadar-kritik\/","title":{"rendered":"Cache-Control, ETag ve CDN \u00d6nbellek Kurallar\u0131"},"content":{"rendered":"<div class=\"dchost-blog-content-wrapper\"><p>Bir WordPress sitesi, bir Laravel API projesi veya modern bir React SPA uygulamas\u0131 geli\u015ftirirken performans konu\u015fulan her toplant\u0131da \u015fu soru mutlaka gelir: Taray\u0131c\u0131 ve CDN \u00f6nbelle\u011fini do\u011fru ayarlasak bu site ne kadar h\u0131zlan\u0131r ve altyap\u0131 maliyeti ne kadar d\u00fc\u015fer? HTTP Cache-Control ba\u015fl\u0131klar\u0131, ETag ve CDN taraf\u0131ndaki \u00f6nbellek kurallar\u0131 do\u011fru kurguland\u0131\u011f\u0131nda, tekrarlanan veri aktar\u0131m\u0131 ve origin y\u00fck\u00fc azalabilir; sayfa y\u00fckleme performans\u0131 da iyile\u015febilir. Bu ba\u015fl\u0131klar\u0131n gere\u011finden agresif kullan\u0131lmas\u0131 eski i\u00e7eri\u011fin g\u00f6sterilmesine, \u00f6nbelleklemenin tamamen kapat\u0131lmas\u0131 ise gereksiz dinamik isteklere yol a\u00e7abilir.<\/p>\n<p>Bu yaz\u0131da HTTP Cache-Control, ETag ve CDN \u00f6nbellek kurallar\u0131n\u0131; WordPress, Laravel ve SPA (React, Vue, Angular) projeleri \u00f6zelinde, ger\u00e7ek\u00e7i senaryolarla ele alaca\u011f\u0131z. Hangi dosyay\u0131 ne kadar s\u00fcre cachelemek mant\u0131kl\u0131, HTML sayfalarda ne kadar agresif olunabilir, API cevaplar\u0131nda ETag ne i\u015fimize yarar, CDN kural\u0131 ile origin sunucu ayarlar\u0131 nas\u0131l uyumlu olmal\u0131 tek tek \u00fczerinden ge\u00e7ece\u011fiz.<\/p>\n<p>\u00d6nbellekleme, site h\u0131z\u0131n\u0131n ve altyap\u0131 maliyetinin en b\u00fcy\u00fck kald\u0131ra\u00e7lar\u0131ndan biri. \u00d6zellikle medya ve statik dosya a\u011f\u0131rl\u0131kl\u0131 projelerde, do\u011fru HTTP ba\u015fl\u0131klar\u0131 ile tekrarlanan indirmeleri ve origin y\u00fck\u00fcn\u00fc azaltmak m\u00fcmk\u00fcn. Taray\u0131c\u0131 CSS ve JS dosyalar\u0131n\u0131 yeniden indirmek zorunda kalmad\u0131\u011f\u0131nda, \u00f6zellikle tekrar ziyaretlerde y\u00fckleme s\u00fcresi ve LCP iyile\u015febilir. G\u00fcncel Core Web Vitals metrikleri LCP, INP ve CLS&#8217;dir; \u00f6nbellekleme tek ba\u015f\u0131na etkile\u015fim yan\u0131t s\u00fcresini veya g\u00f6rsel kararl\u0131l\u0131\u011f\u0131 iyile\u015ftirmeyi garanti etmez. Bu konuyu daha derinlemesine okumak isterseniz, <a href='https:\/\/www.dchost.com\/blog\/hosting-ttfb-lcp-cls-performansi\/'>Core Web Vitals ve hosting altyap\u0131s\u0131n\u0131n etkile\u015fimi<\/a> ba\u015fl\u0131kl\u0131 rehberimize g\u00f6z atabilirsiniz.<\/p>\n<p>Di\u011fer tarafta CDN kullan\u0131yorsan\u0131z, edge sunuculardaki cache hit oran\u0131 origin y\u00fck\u00fcn\u00fc etkiler; faturaya etkisi ise CDN ve origin \u00fccretlendirmesine ba\u011fl\u0131d\u0131r. K\u00f6t\u00fc kurgulanm\u0131\u015f Cache-Control ba\u015fl\u0131klar\u0131, CDN katman\u0131n\u0131n HTML ve API cevaplar\u0131n\u0131 yanl\u0131\u015f \u015fekilde cachelemesine, kullan\u0131c\u0131 ba\u015f\u0131na ki\u015fiselle\u015ftirilmi\u015f i\u00e7eriklerin kar\u0131\u015fmas\u0131na ve login sayfalar\u0131n\u0131n statikmi\u015f gibi saklanmas\u0131na neden olabilir. Bu y\u00fczden, taray\u0131c\u0131 \u00f6nbelle\u011fini d\u00fc\u015f\u00fcn\u00fcrken her zaman CDN ile beraber, u\u00e7tan uca bir strateji kurmak gerekiyor. Y\u00fcksek trafikli WordPress ve Laravel projelerinde, hangi yan\u0131t\u0131n hangi katmanda saklanaca\u011f\u0131n\u0131 g\u00f6steren bir HTTP \u00f6nbellek ba\u015fl\u0131klar\u0131 haritas\u0131 bu stratejiyi somutla\u015ft\u0131r\u0131r.<\/p>\n<div id=\"toc_container\" role=\"navigation\" aria-label=\"Table of Contents\" data-nosnippet class=\"toc_transparent no_bullets toc_numbered toc_title_center\"><p class=\"toc_title\">\u0130\u00e7indekiler<\/p><ul class=\"toc_list\"><li><a href=\"#HTTP_Cache-Control_Direktiflerini_Dogru_Okumak\"><span class=\"toc_number toc_depth_1\">1.<\/span> HTTP Cache-Control Direktiflerini Do\u011fru Okumak<\/a><ul><li><a href=\"#Temel_Cache-Control_direktifleri\"><span class=\"toc_number toc_depth_2\">1.1.<\/span> Temel Cache-Control direktifleri<\/a><\/li><li><a href=\"#Gelismis_direktifler_stale-while-revalidate_ve_stale-if-error\"><span class=\"toc_number toc_depth_2\">1.2.<\/span> Geli\u015fmi\u015f direktifler: stale-while-revalidate ve stale-if-error<\/a><\/li><\/ul><\/li><li><a href=\"#ETag_ve_Last-Modified_ile_Kosullu_Istekler\"><span class=\"toc_number toc_depth_1\">2.<\/span> ETag ve Last-Modified ile Ko\u015fullu \u0130stekler<\/a><ul><li><a href=\"#ETag_nedir_nasil_calisir\"><span class=\"toc_number toc_depth_2\">2.1.<\/span> ETag nedir, nas\u0131l \u00e7al\u0131\u015f\u0131r<\/a><\/li><li><a href=\"#Last-Modified_ile_birlikte_kullanim_ve_CDN_etkisi\"><span class=\"toc_number toc_depth_2\">2.2.<\/span> Last-Modified ile birlikte kullan\u0131m ve CDN etkisi<\/a><\/li><\/ul><\/li><li><a href=\"#WordPress_Icin_Dogru_Tarayici_Onbellekleme_Stratejisi\"><span class=\"toc_number toc_depth_1\">3.<\/span> WordPress \u0130\u00e7in Do\u011fru Taray\u0131c\u0131 \u00d6nbellekleme Stratejisi<\/a><ul><li><a href=\"#Statik_dosyalar_CSS_JS_gorseller_ve_yazi_tipleri\"><span class=\"toc_number toc_depth_2\">3.1.<\/span> Statik dosyalar: CSS, JS, g\u00f6rseller ve yaz\u0131 tipleri<\/a><\/li><li><a href=\"#HTML_sayfalar_WooCommerce_sayfalari_ve_kullaniciya_ozel_icerik\"><span class=\"toc_number toc_depth_2\">3.2.<\/span> HTML sayfalar, WooCommerce sayfalar\u0131 ve kullan\u0131c\u0131ya \u00f6zel i\u00e7erik<\/a><\/li><li><a href=\"#Nginx_icin_ornek_WordPress_onbellek_ayrimi\"><span class=\"toc_number toc_depth_2\">3.3.<\/span> Nginx i\u00e7in \u00f6rnek WordPress \u00f6nbellek ayr\u0131m\u0131<\/a><\/li><\/ul><\/li><li><a href=\"#Laravel_Uygulamalarinda_Cache-Control_ve_ETag\"><span class=\"toc_number toc_depth_1\">4.<\/span> Laravel Uygulamalar\u0131nda Cache-Control ve ETag<\/a><ul><li><a href=\"#Asset_versiyonlama_mix_ve_vite_kullanimi\"><span class=\"toc_number toc_depth_2\">4.1.<\/span> Asset versiyonlama: mix ve vite kullan\u0131m\u0131<\/a><\/li><li><a href=\"#API_cevaplari_icin_Cache-Control_ve_ETag_stratejisi\"><span class=\"toc_number toc_depth_2\">4.2.<\/span> API cevaplar\u0131 i\u00e7in Cache-Control ve ETag stratejisi<\/a><\/li><\/ul><\/li><li><a href=\"#SPA_Projeleri_React_Vue_Angular_Icin_Onbellek_Kurallari\"><span class=\"toc_number toc_depth_1\">5.<\/span> SPA Projeleri (React, Vue, Angular) \u0130\u00e7in \u00d6nbellek Kurallar\u0131<\/a><ul><li><a href=\"#indexhtml_icin_kisa_sureli_fakat_kontrollu_cache\"><span class=\"toc_number toc_depth_2\">5.1.<\/span> index.html i\u00e7in k\u0131sa s\u00fcreli fakat kontroll\u00fc cache<\/a><\/li><li><a href=\"#Hashli_JS_ve_CSS_dosyalari_icin_agresif_cache\"><span class=\"toc_number toc_depth_2\">5.2.<\/span> Hashli JS ve CSS dosyalar\u0131 i\u00e7in agresif cache<\/a><\/li><li><a href=\"#Service_Worker_offline_cache_ve_CDN_uyumu\"><span class=\"toc_number toc_depth_2\">5.3.<\/span> Service Worker, offline cache ve CDN uyumu<\/a><\/li><\/ul><\/li><li><a href=\"#CDN_ile_Origin_Onbellegini_Uyumlu_Hale_Getirmek\"><span class=\"toc_number toc_depth_1\">6.<\/span> CDN ile Origin \u00d6nbelle\u011fini Uyumlu Hale Getirmek<\/a><ul><li><a href=\"#Cache_key_cookie_ve_Vary_basliklari\"><span class=\"toc_number toc_depth_2\">6.1.<\/span> Cache key, cookie ve Vary ba\u015fl\u0131klar\u0131<\/a><\/li><li><a href=\"#Origin_ve_CDN_arasinda_rol_dagilimi\"><span class=\"toc_number toc_depth_2\">6.2.<\/span> Origin ve CDN aras\u0131nda rol da\u011f\u0131l\u0131m\u0131<\/a><\/li><\/ul><\/li><li><a href=\"#Ornek_Onbellekleme_Senaryolari_WordPress_Laravel_API_ve_SPA\"><span class=\"toc_number toc_depth_1\">7.<\/span> \u00d6rnek \u00d6nbellekleme Senaryolar\u0131: WordPress, Laravel API ve SPA<\/a><ul><li><a href=\"#1_Klasik_blog_veya_kurumsal_WordPress_sitesi\"><span class=\"toc_number toc_depth_2\">7.1.<\/span> 1. Klasik blog veya kurumsal WordPress sitesi<\/a><\/li><li><a href=\"#2_Laravel_tabanli_API_admin_panel\"><span class=\"toc_number toc_depth_2\">7.2.<\/span> 2. Laravel tabanl\u0131 API + admin panel<\/a><\/li><li><a href=\"#3_SPA_frontend_ayri_API_sunucusu\"><span class=\"toc_number toc_depth_2\">7.3.<\/span> 3. SPA frontend + ayr\u0131 API sunucusu<\/a><\/li><\/ul><\/li><li><a href=\"#Sonuc_HTTP_Onbellegi_Dogru_Kuruldugunda_Ne_Kazanirsiniz\"><span class=\"toc_number toc_depth_1\">8.<\/span> Sonu\u00e7: HTTP \u00d6nbelle\u011fi Do\u011fru Kuruldu\u011funda Ne Kazan\u0131rs\u0131n\u0131z<\/a><\/li><\/ul><\/div>\n<h2><span id=\"HTTP_Cache-Control_Direktiflerini_Dogru_Okumak\">HTTP Cache-Control Direktiflerini Do\u011fru Okumak<\/span><\/h2>\n<p>Cache-Control ba\u015fl\u0131\u011f\u0131, taray\u0131c\u0131n\u0131n ve ara \u00f6nbelleklerin (CDN, reverse proxy vb.) i\u00e7eri\u011fi nas\u0131l saklayaca\u011f\u0131n\u0131 belirleyen anahtar mekanizma. Temel ve geli\u015fmi\u015f direktifleri netle\u015ftirelim.<\/p>\n<h3><span id=\"Temel_Cache-Control_direktifleri\">Temel Cache-Control direktifleri<\/span><\/h3>\n<ul>\n<li><strong>max-age=sek<\/strong>: \u0130\u00e7eri\u011fin ka\u00e7 saniye boyunca taze kabul edilece\u011fini belirtir. \u00d6rne\u011fin 86400 bir g\u00fcn demektir.<\/li>\n<li><strong>s-maxage=sek<\/strong>: Payla\u015f\u0131ml\u0131 cacheler (CDN, proxy) i\u00e7in max-age de\u011ferini override eder. Taray\u0131c\u0131 farkl\u0131, CDN farkl\u0131 s\u00fcre kullanabilir.<\/li>\n<li><strong>public<\/strong>: Cevab\u0131n, payla\u015f\u0131ml\u0131 cacheler taraf\u0131ndan saklanabilece\u011fini s\u00f6yler. HTML sayfalar\u0131 i\u00e7in dikkatli kullan\u0131lmal\u0131d\u0131r.<\/li>\n<li><strong>private<\/strong>: Cevab\u0131n taray\u0131c\u0131 gibi \u00f6zel \u00f6nbelleklerde saklanmas\u0131na izin verir, payla\u015f\u0131ml\u0131 cachelerde saklanmas\u0131n\u0131 engeller. Kullan\u0131c\u0131ya \u00f6zel i\u00e7eriklerde kullan\u0131labilir; saklanmamas\u0131 gereken hassas yan\u0131tlar i\u00e7in tek ba\u015f\u0131na yeterli de\u011fildir.<\/li>\n<li><strong>no-store<\/strong>: HTTP \u00f6nbelleklerine yan\u0131t\u0131 saklamamalar\u0131n\u0131 s\u00f6yler. \u00d6deme sayfalar\u0131 ve saklanmamas\u0131 gereken hassas veriler i\u00e7in uygundur; uygulaman\u0131n t\u00fcm disk veya bellek kullan\u0131m\u0131n\u0131 engelleyen bir g\u00fcvenlik mekanizmas\u0131 de\u011fildir.<\/li>\n<li><strong>no-cache<\/strong>: \u0130sim kafa kar\u0131\u015ft\u0131r\u0131c\u0131; asl\u0131nda cachelemeyi tamamen kapatmak de\u011fildir. \u0130\u00e7eri\u011fin cachelenebilece\u011fini ancak her kullan\u0131mda origin ile yeniden do\u011frulanmas\u0131 gerekti\u011fini s\u00f6yler (ETag veya Last-Modified ile).<\/li>\n<\/ul>\n<p>Pratikte herkese a\u00e7\u0131k, s\u00fcr\u00fcmlenmi\u015f statik dosyalar i\u00e7in public ve uzun max-age kullan\u0131labilir. Kullan\u0131c\u0131ya \u00f6zel HTML ve API yan\u0131tlar\u0131nda yerel saklama uygunsa private ile k\u0131sa max-age, saklama istenmiyorsa no-store se\u00e7ilir; no-store ile max-age eklemek k\u0131sa s\u00fcreli saklama sa\u011flamaz. Ki\u015fiselle\u015ftirilmemi\u015f WordPress ana sayfas\u0131nda 60 saniyelik mikro \u00f6nbellekleme makul olabilir. Logo PNG i\u00e7in 30 g\u00fcn ise ancak de\u011fi\u015fiklikte URL yenileniyorsa veya bu kadar eski i\u00e7erik kabul edilebiliyorsa uygundur.<\/p>\n<h3><span id=\"Gelismis_direktifler_stale-while-revalidate_ve_stale-if-error\">Geli\u015fmi\u015f direktifler: stale-while-revalidate ve stale-if-error<\/span><\/h3>\n<p>Taray\u0131c\u0131 ve CDN deste\u011fi de\u011fi\u015febilmekle birlikte, iki \u00f6nemli ek direktif \u015funlard\u0131r:<\/p>\n<ul>\n<li><strong>stale-while-revalidate=sek<\/strong>: Yan\u0131t\u0131n tazelik s\u00fcresi dolduktan sonra belirtilen ek s\u00fcre i\u00e7inde, arka planda yeniden do\u011frulama yap\u0131l\u0131rken eski kopyan\u0131n sunulmas\u0131na izin verir.<\/li>\n<li><strong>stale-if-error=sek<\/strong>: Ba\u011flant\u0131 sorunu veya desteklenen sunucu hatalar\u0131nda, yan\u0131t\u0131n tazelik s\u00fcresi dolduktan sonra belirtilen ek s\u00fcre i\u00e7inde eski kopyan\u0131n sunulmas\u0131na izin verir.<\/li>\n<\/ul>\n<p>Bu mekanizmalar, \u00f6zellikle CDN seviyesinde kullan\u0131ld\u0131\u011f\u0131nda kesintisiz yay\u0131na ciddi katk\u0131 sa\u011flar. Bu konuyu daha \u00f6nce <a href='https:\/\/www.dchost.com\/blog\/kesinti-caninizi-sikmasin-stale-while-revalidate-ve-stale-if-error\/'>stale-while-revalidate ve stale-if-error direktiflerinin pratik kullan\u0131m\u0131<\/a> ba\u015fl\u0131kl\u0131 yaz\u0131m\u0131zda detayl\u0131 anlatm\u0131\u015ft\u0131k. Buradaki fikir \u015fu: Origin k\u0131sa s\u00fcreli bir problem ya\u015fad\u0131\u011f\u0131nda, uygun ve izin verilen s\u00fcre i\u00e7inde bir \u00f6nbellek kopyas\u0131 varsa baz\u0131 istekler origin yan\u0131t\u0131 beklenmeden kar\u015f\u0131lanabilir.<\/p>\n<h2><span id=\"ETag_ve_Last-Modified_ile_Kosullu_Istekler\">ETag ve Last-Modified ile Ko\u015fullu \u0130stekler<\/span><\/h2>\n<p>Cache-Control ile ne kadar s\u00fcre cachelenece\u011fini belirledik. Peki \u00f6nbellekteki yan\u0131t yeniden do\u011frulan\u0131rken i\u00e7eri\u011fin de\u011fi\u015fip de\u011fi\u015fmedi\u011fi nas\u0131l anla\u015f\u0131l\u0131r? ETag ve Last-Modified burada devreye girer; taze say\u0131lan bir kopyay\u0131 kendili\u011finden ge\u00e7ersiz k\u0131lmazlar.<\/p>\n<h3><span id=\"ETag_nedir_nasil_calisir\">ETag nedir, nas\u0131l \u00e7al\u0131\u015f\u0131r<\/span><\/h3>\n<p>ETag, sunucunun bir kayna\u011f\u0131n belirli g\u00f6sterimi i\u00e7in sa\u011flayabildi\u011fi s\u00fcr\u00fcm etiketidir; her yan\u0131tta bulunmas\u0131 gerekmez. \u0130\u00e7erik hashinden veya dosya metaverilerinden t\u00fcretilebilir. \u0130stemci, saklad\u0131\u011f\u0131 yan\u0131t\u0131 yeniden do\u011frulayan bir GET veya HEAD iste\u011finde etiketi If-None-Match ba\u015fl\u0131\u011f\u0131yla g\u00f6nderir. Etiket g\u00fcncel g\u00f6sterimle e\u015fle\u015firse sunucu 304 Not Modified d\u00f6nd\u00fcrebilir; yan\u0131t g\u00f6vdesi yeniden indirilmez ve \u00f6nbellekteki kopyan\u0131n ba\u015fl\u0131klar\u0131 g\u00fcncellenir.<\/p>\n<p>Bu mekanizma \u00f6zellikle \u015fu durumlarda \u00e7ok de\u011ferlidir:<\/p>\n<ul>\n<li>max-age s\u00fcresi nispeten k\u0131sa tutulmak zorundaysa bile gereksiz veri transferini azaltmak<\/li>\n<li>API cevaplar\u0131nda veri de\u011fi\u015fmediyse aktar\u0131m\u0131 azaltmak; ETag yan\u0131t g\u00f6vdesi \u00fcretilmeden hesaplanabiliyorsa CPU maliyetini de d\u00fc\u015f\u00fcrmek<\/li>\n<li>Dinamik HTML sayfalarda, de\u011fi\u015fiklik olmayan kullan\u0131c\u0131lar i\u00e7in daha h\u0131zl\u0131 yan\u0131t sa\u011flamak<\/li>\n<\/ul>\n<h3><span id=\"Last-Modified_ile_birlikte_kullanim_ve_CDN_etkisi\">Last-Modified ile birlikte kullan\u0131m ve CDN etkisi<\/span><\/h3>\n<p>Last-Modified ba\u015fl\u0131\u011f\u0131, i\u00e7eri\u011fin son de\u011fi\u015ftirilme zaman\u0131n\u0131 belirtir. Taray\u0131c\u0131 yeniden do\u011frulayan bir GET veya HEAD iste\u011finde If-Modified-Since g\u00f6nderebilir; i\u00e7erik belirtilen tarihten beri de\u011fi\u015fmemi\u015fse 304 d\u00f6nd\u00fcr\u00fclebilir. \u0130stekte If-None-Match de varsa de\u011ferlendirmede o \u00f6nceliklidir. ETag ve Last-Modified genelde birlikte kullan\u0131l\u0131r; baz\u0131 durumlarda sadece Last-Modified yeterli olabilir.<\/p>\n<p>CDN taraf\u0131nda ise dikkat edilmesi gereken nokta \u015fudur: Baz\u0131 CDNler, ETag ba\u015fl\u0131klar\u0131n\u0131 manip\u00fcle edebilir veya origin ile edge aras\u0131nda farkl\u0131la\u015ft\u0131rabilir. Ayr\u0131ca ETag de\u011feriniz sunucudaki dosyan\u0131n inode bilgisinden t\u00fcretiliyorsa, \u00e7oklu sunucu mimarilerinde (\u00f6rne\u011fin birden fazla web sunucusuna da\u011f\u0131t\u0131lm\u0131\u015f varsay\u0131msal bir WordPress k\u00fcmesi) ayn\u0131 i\u00e7eri\u011fe farkl\u0131 ETagler \u00fcretilebilir. Bu da gereksiz yeniden indirmelere yol a\u00e7abilir. Bu y\u00fczden ayn\u0131 g\u00f6sterim i\u00e7in sunucular aras\u0131nda tutarl\u0131, g\u00f6sterim de\u011fi\u015fti\u011finde ise de\u011fi\u015fen etiketler kullan\u0131lmal\u0131d\u0131r. \u0130\u00e7erik tabanl\u0131 hashler veya statik dosyalar i\u00e7in build s\u0131ras\u0131nda \u00fcretilen s\u00fcr\u00fcme \u00f6zg\u00fc etiketler bu ama\u00e7la de\u011ferlendirilebilir.<\/p>\n<h2><span id=\"WordPress_Icin_Dogru_Tarayici_Onbellekleme_Stratejisi\">WordPress \u0130\u00e7in Do\u011fru Taray\u0131c\u0131 \u00d6nbellekleme Stratejisi<\/span><\/h2>\n<p>WordPress i\u00e7in \u00f6nbellekleme tasarlarken statik varl\u0131klar ile HTML \u00e7\u0131kt\u0131lar\u0131 ayr\u0131 de\u011ferlendirilmelidir. Statik dosyalarda s\u00fcr\u00fcmleme ve uzun saklama s\u00fcreleri, HTML&#8217;de ise i\u00e7eri\u011fin herkese a\u00e7\u0131k m\u0131 yoksa kullan\u0131c\u0131ya \u00f6zel mi oldu\u011fu belirleyicidir.<\/p>\n<h3><span id=\"Statik_dosyalar_CSS_JS_gorseller_ve_yazi_tipleri\">Statik dosyalar: CSS, JS, g\u00f6rseller ve yaz\u0131 tipleri<\/span><\/h3>\n<p>WordPress tema ve eklentileriniz \u00e7o\u011funlukla versiyon parametreleri ile cache busting uygular. \u00d6rne\u011fin style.css dosyan\u0131z \u015fu \u015fekilde \u00e7a\u011fr\u0131l\u0131r:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">\/wp-content\/themes\/tema\/style.css?ver=1.4.3<\/code><\/pre>\n<p>Dosya de\u011fi\u015fti\u011finde ver parametresi de g\u00fcncellenir ve CDN bu parametreyi cache key i\u00e7inde tutarsa, yeni URL yeni kopyan\u0131n al\u0131nmas\u0131n\u0131 sa\u011flar. Bir y\u0131ll\u0131k saklama s\u00fcresi ancak bu s\u00fcr\u00fcmleme d\u00fczeni g\u00fcvenilir bi\u00e7imde uygulan\u0131yorsa uygundur; dosyan\u0131n de\u011fi\u015fmesi tek ba\u015f\u0131na ver de\u011ferini otomatik g\u00fcncellemez.<\/p>\n<p>A\u015fa\u011f\u0131daki uzun s\u00fcreli politika yaln\u0131zca herkese a\u00e7\u0131k ve her i\u00e7erik de\u011fi\u015fiminde URL&#8217;si yenilenen statik varl\u0131klar i\u00e7indir. Nginx \u00f6rne\u011findeki uzant\u0131 e\u015fle\u015fmesi s\u00fcr\u00fcmlemeyi denetlemez; e\u015fle\u015fen t\u00fcm dosyalar\u0131n bu ko\u015fulu sa\u011flamas\u0131 gerekir. Bu \u00f6rnek Nginx\u2019in do\u011frudan sundu\u011fu statik dosyalar i\u00e7indir. <code>expires off<\/code>, expires mod\u00fcl\u00fcn\u00fcn ikinci bir max-age \u00fcretmesini engeller; politikay\u0131 <code>add_header<\/code> verir. \u00dcst d\u00fczey <code>add_header<\/code> kal\u0131t\u0131m\u0131n\u0131, korunmas\u0131 gereken g\u00fcvenlik ba\u015fl\u0131klar\u0131n\u0131 ve di\u011fer mod\u00fcl\/CDN ba\u015fl\u0131klar\u0131n\u0131 kontrol edin; off \u00f6nceden eklenmi\u015f ba\u015fl\u0131klar\u0131 silmez. Uygulamadan \u00f6nce yap\u0131land\u0131rmay\u0131 ve origin\/CDN yan\u0131t\u0131nda tek, tutarl\u0131 Cache-Control politikas\u0131n\u0131 do\u011frulay\u0131n.<\/p>\n<ul>\n<li>CSS, JS, font ve g\u00f6rseller i\u00e7in: Cache-Control public, max-age=2592000 (30 g\u00fcn) veya daha uzun<\/li>\n<li>immutable direktifi, yan\u0131t taze kald\u0131\u011f\u0131 s\u00fcrece yeniden do\u011frulama ihtiyac\u0131n\u0131 azalt\u0131r. Bunu yaln\u0131zca ayn\u0131 URL alt\u0131nda i\u00e7eri\u011fin de\u011fi\u015fmeyece\u011fi varl\u0131klarda kullan\u0131n; g\u00fcncellemede dosya ad\u0131n\u0131 veya cache key&#8217;e dahil edilen s\u00fcr\u00fcm parametresini de\u011fi\u015ftirin.<\/li>\n<\/ul>\n<pre class=\"language-nginx line-numbers\"><code class=\"language-nginx\">location ~* \\.(css|js|png|jpe?g|gif|svg|webp|ico|woff2?)$ {\n    expires off;\n    add_header Cache-Control &#039;public, max-age=2592000, immutable&#039;;\n}<\/code><\/pre>\n<p>G\u00f6rsel optimizasyonu ve CDN taraf\u0131ndaki ayarlarla birlikte d\u00fc\u015f\u00fcnmek isterseniz, <a href='https:\/\/www.dchost.com\/blog\/gorsel-seo-webp-avif-cdn-ve-gorsel-site-haritasi\/'>WebP, AVIF ve CDN alt alan adlar\u0131 ile g\u00f6rsel SEO stratejileri<\/a> yaz\u0131s\u0131ndaki \u00f6nerilerle bu ayarlar\u0131 birle\u015ftirebilirsiniz.<\/p>\n<h3><span id=\"HTML_sayfalar_WooCommerce_sayfalari_ve_kullaniciya_ozel_icerik\">HTML sayfalar, WooCommerce sayfalar\u0131 ve kullan\u0131c\u0131ya \u00f6zel i\u00e7erik<\/span><\/h3>\n<p>HTML taraf\u0131nda ise biraz daha dikkatli olmak \u015fart. Ana sayfa, kategori sayfalar\u0131 ve blog yaz\u0131lar\u0131 i\u00e7in tam sayfa \u00f6nbellekleme (server side cache) kullan\u0131yorsan\u0131z, taray\u0131c\u0131ya uzun s\u00fcreli cache s\u00fcresi vermenize \u00e7o\u011fu zaman gerek kalmaz. Burada ama\u00e7 taray\u0131c\u0131dan \u00e7ok, sunucuyu rahatlatan reverse proxy veya uygulama i\u00e7i cachelerdir. Yine de herkese ayn\u0131 i\u00e7eri\u011fi sunan anonim yan\u0131tlar i\u00e7in 30 ila 120 saniyelik mikro \u00f6nbellekleme de\u011ferlendirilebilir. Taray\u0131c\u0131 tazeli\u011fini max-age, payla\u015f\u0131ml\u0131 HTTP \u00f6nbelle\u011finin tazeli\u011fini s-maxage ile ayr\u0131 y\u00f6netebilirsiniz. Oturum a\u00e7m\u0131\u015f kullan\u0131c\u0131lar\u0131n, sepet\/\u00f6deme\/hesap sayfalar\u0131n\u0131n ve di\u011fer ki\u015fiselle\u015ftirilmi\u015f yan\u0131tlar\u0131n payla\u015f\u0131ml\u0131 \u00f6nbelle\u011fi atlamas\u0131 gerekir; k\u0131sa s\u00fcre se\u00e7mek bu ayr\u0131m\u0131n yerine ge\u00e7mez.<\/p>\n<p>WooCommerce taraf\u0131nda ise sepet, \u00f6deme ve hesap sayfalar\u0131 kesinlikle public cachelenmemelidir. Bu sayfalar i\u00e7in:<\/p>\n<ul>\n<li>Cache-Control no-store, no-cache, must-revalidate<\/li>\n<li>Pragma no-cache (eski taray\u0131c\u0131lar i\u00e7in)<\/li>\n<li>Vary: Cookie veya Vary: Authorization \u00f6nbellek varyantlar\u0131n\u0131 ay\u0131r\u0131r; saklamay\u0131 engellemez. Bu sayfalar CDN kurallar\u0131nda da \u00f6nbellek d\u0131\u015f\u0131nda b\u0131rak\u0131lmal\u0131d\u0131r<\/li>\n<\/ul>\n<p>CDN ve edge kurallar\u0131 ile HTML cachei y\u00f6netmek \u00fczerine daha odakl\u0131 bir rehbere ihtiyac\u0131n\u0131z varsa, <a href='https:\/\/www.dchost.com\/blog\/wordpress-cdn-woocommerce-html-cache-bypass\/'>WordPress i\u00e7in CDN \u00f6nbellek kurallar\u0131 ve WooCommercede HTML cache bypass stratejileri<\/a> yaz\u0131m\u0131z\u0131 da bu makale ile birlikte okuman\u0131z\u0131 \u00f6neririm.<\/p>\n<h3><span id=\"Nginx_icin_ornek_WordPress_onbellek_ayrimi\">Nginx i\u00e7in \u00f6rnek WordPress \u00f6nbellek ayr\u0131m\u0131<\/span><\/h3>\n<p>Nginx \u00fczerinde statik dosyalar ile dinamik PHP yan\u0131tlar\u0131 ayr\u0131 ele al\u0131nabilir. A\u015fa\u011f\u0131daki par\u00e7a tam bir WordPress yap\u0131land\u0131rmas\u0131 de\u011fildir; mevcut PHP konumunu ve y\u00f6nlendirme kurallar\u0131n\u0131 inceleyerek birle\u015ftirin.<\/p>\n<p>Statik e\u015fle\u015fme yaln\u0131zca herkese a\u00e7\u0131k dosyalar\u0131 kapsamal\u0131d\u0131r. Genel uzant\u0131 \u00f6rne\u011finde immutable yoktur: s\u00fcr\u00fcmlenmemi\u015f dosyay\u0131 ayn\u0131 URL alt\u0131nda de\u011fi\u015ftirirseniz 30 g\u00fcnl\u00fck tazelik s\u00fcresi bitmeden g\u00fcncellenmeyebilir; ihtiyaca g\u00f6re s\u00fcreyi k\u0131salt\u0131n veya URL s\u00fcr\u00fcmleyin.<\/p>\n<p>PHP \u00f6rne\u011fi, Nginx ve PHP-FPM&#8217;in ayn\u0131 dosya yolunu g\u00f6rd\u00fc\u011f\u00fc root tabanl\u0131 kurulum i\u00e7indir; alias veya farkl\u0131 konteyner yollar\u0131nda SCRIPT_FILENAME e\u015flemesini uyarlay\u0131n. fastcgi_params i\u00e7inde gerekli istek parametrelerini ve yinelenmeyen SCRIPT_FILENAME tan\u0131m\u0131n\u0131 do\u011frulay\u0131n; php-fpm:9000 adresini ger\u00e7ek havuz soketi\/adresiyle de\u011fi\u015ftirin.<\/p>\n<p>PHP i\u00e7in \u00f6nceki Cache-Control\/Expires yan\u0131t ba\u015fl\u0131klar\u0131 bilin\u00e7li olarak bast\u0131r\u0131l\u0131r; bu, etkin origin veya CDN \u00f6nbelle\u011fini kendili\u011finden devre d\u0131\u015f\u0131 b\u0131rakmaz. Kullan\u0131c\u0131ya \u00f6zel yan\u0131tlar i\u00e7in saklama ve yeniden kullan\u0131m bypass kurallar\u0131n\u0131 ayr\u0131ca do\u011frulay\u0131n. \u00dcst d\u00fczey add_header kal\u0131t\u0131m\u0131 ve g\u00fcvenlik ba\u015fl\u0131klar\u0131 korunmal\u0131, son origin\/CDN yan\u0131t\u0131nda tek tutarl\u0131 politika g\u00f6r\u00fclmelidir. Uygulamadan \u00f6nce yap\u0131land\u0131rmay\u0131 ve yan\u0131t ba\u015fl\u0131klar\u0131n\u0131 test edin:<\/p>\n<pre class=\"language-nginx line-numbers\"><code class=\"language-nginx\"># Yaln\u0131zca herkese a\u00e7\u0131k statik dosyalar; genel \u00f6rnekte immutable yok\nlocation ~* \\.(css|js|png|jpe?g|gif|svg|webp|ico|woff2?)$ {\n    expires off;\n    add_header Cache-Control &#039;public, max-age=2592000&#039;;\n}\n\n# Mevcut root tabanl\u0131 PHP konumuyla birle\u015ftirilecek \u00f6rnek\nlocation ~ \\.php$ {\n    try_files $uri =404;\n    expires off;\n    fastcgi_hide_header Cache-Control;\n    fastcgi_hide_header Expires;\n    add_header Cache-Control &#039;private, no-cache, no-store, must-revalidate&#039; always;\n    include fastcgi_params;\n    fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;\n    fastcgi_pass php-fpm:9000;\n}<\/code><\/pre>\n<p>Tabii ki burada php-fpm havuz ayarlar\u0131 ve OPcache yap\u0131land\u0131rmas\u0131n\u0131n da devreye girdi\u011fini unutmayal\u0131m. Sunucu taraf\u0131 WordPress optimizasyonu i\u00e7in, <a href='https:\/\/www.dchost.com\/blog\/wordpress-sunucu-optimizasyonu-php-redis-mysql\/'>PHP-FPM, OPcache ve Redis ile WordPress optimizasyon rehberimizi<\/a> inceleyebilirsiniz. Herkese a\u00e7\u0131k HTML i\u00e7in tam sayfa cache, s\u00fcr\u00fcmlenmi\u015f statik dosyalar i\u00e7in uzun s\u00fcreli cache ile birlikte kullan\u0131labilir; kullan\u0131c\u0131ya \u00f6zel sayfalar bu kapsam\u0131n d\u0131\u015f\u0131nda tutulmal\u0131d\u0131r.<\/p>\n<h2><span id=\"Laravel_Uygulamalarinda_Cache-Control_ve_ETag\">Laravel Uygulamalar\u0131nda Cache-Control ve ETag<\/span><\/h2>\n<p>Laravel hem klasik web uygulamalar\u0131nda hem de API servislerinde kullan\u0131labilir. Uygulama i\u00e7i \u00f6nbellekleme ile HTTP \u00f6nbelleklemesi farkl\u0131 katmanlard\u0131r ve ayr\u0131 de\u011ferlendirilmelidir.<\/p>\n<h3><span id=\"Asset_versiyonlama_mix_ve_vite_kullanimi\">Asset versiyonlama: mix ve vite kullan\u0131m\u0131<\/span><\/h3>\n<p>\u00d6nce, statik dosyalardan ba\u015flayal\u0131m. Mix veya Vite kullan\u0131lan bir projede \u00e7\u0131kt\u0131 URL&#8217;lerinin nas\u0131l s\u00fcr\u00fcmlendi\u011fini belirleyin. A\u015fa\u011f\u0131daki yollar, i\u00e7erik hashinin dosya ad\u0131na eklendi\u011fi bir d\u00fczenin temsili \u00f6rnekleridir; iki arac\u0131n ortak varsay\u0131lan \u00e7\u0131kt\u0131s\u0131 de\u011fildir:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">\/build\/assets\/app.7c3f9a2d.js\n\/build\/assets\/app.19b5c811.css<\/code><\/pre>\n<p>Bu hashli dosya isimleri, agresif taray\u0131c\u0131 ve CDN cachei i\u00e7in bi\u00e7ilmi\u015f kaftand\u0131r. \u00c7\u00fcnk\u00fc dosya i\u00e7eri\u011fi de\u011fi\u015fti\u011finde isim de de\u011fi\u015fir; eski isimli dosyalar cachete kalsa bile g\u00fcncel HTML veya manifest yeni dosya ad\u0131na ba\u015fvurdu\u011funda yeni versiyon \u00e7a\u011fr\u0131l\u0131r.<\/p>\n<p>Bu durumda, Nginx veya Apache seviyesinde \u015fu mant\u0131kla hareket edebilirsiniz:<\/p>\n<ul>\n<li>Yaln\u0131zca herkese a\u00e7\u0131k, i\u00e7erik hashli ve ayn\u0131 URL alt\u0131nda de\u011fi\u015ftirilmeyen assetler i\u00e7in public, max-age=31536000, immutable; build, public veya storage dizinlerinin tamam\u0131na k\u00f6rlemesine uygulanmamal\u0131d\u0131r<\/li>\n<li>S\u0131k de\u011fi\u015fmeyen fakat hashlenmemi\u015f dosyalar i\u00e7in max-age daha k\u0131sa<\/li>\n<\/ul>\n<p>Bu yap\u0131, \u00f6nbellek isabetlerinde b\u00fcy\u00fck JS dosyalar\u0131n\u0131n yeniden aktar\u0131lmas\u0131n\u0131 \u00f6nleyerek a\u011f trafi\u011fini ve origin isteklerini azaltabilir. CPU y\u00fck\u00fcne etkisi, dosyalar\u0131n nas\u0131l sunuldu\u011funa ve \u00f6nbellek isabet oran\u0131na ba\u011fl\u0131d\u0131r.<\/p>\n<h3><span id=\"API_cevaplari_icin_Cache-Control_ve_ETag_stratejisi\">API cevaplar\u0131 i\u00e7in Cache-Control ve ETag stratejisi<\/span><\/h3>\n<p>Laravel ile yaz\u0131lm\u0131\u015f APIlerde, GET istekleri i\u00e7in ETag ve k\u0131sa s\u00fcreli max-age kombinasyonu \u00e7ok i\u015fe yarar. \u00d6rne\u011fin herkese ayn\u0131 \u00fcr\u00fcn listesini veya sabit referans verilerini d\u00f6nen, ki\u015fisel bilgi i\u00e7ermeyen u\u00e7 noktalar i\u00e7in \u015fu stratejiyi izleyebilirsiniz:<\/p>\n<ul>\n<li>Cache-Control public, max-age=60, stale-while-revalidate=30<\/li>\n<li>\u0130stemcinin If-None-Match de\u011feri mevcut ETag ile e\u015fle\u015fen ko\u015fullu GET isteklerinde 304 Not Modified d\u00f6nd\u00fcrmek<\/li>\n<li>Yetkilendirme gerektiren u\u00e7 noktalar i\u00e7in ise private ve genelde no-store kullanmak<\/li>\n<\/ul>\n<p>Laravelde herkese a\u00e7\u0131k bir response i\u00e7in ETag ba\u015fl\u0131\u011f\u0131 a\u015fa\u011f\u0131daki gibi eklenebilir. Bu par\u00e7a yaln\u0131zca ba\u015fl\u0131\u011f\u0131 ekler; ko\u015fullu iste\u011fi de\u011ferlendirip gerekti\u011finde 304 d\u00f6nd\u00fcrme ad\u0131m\u0131 ayr\u0131ca uygulanmal\u0131d\u0131r:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">return response($content)\n    -&gt;header(&#039;Cache-Control&#039;, &#039;public, max-age=60, stale-while-revalidate=30&#039;)\n    -&gt;setEtag(sha1($content));<\/code><\/pre>\n<p>Tabii ger\u00e7ek d\u00fcnyada ETagi sadece i\u00e7erikten de\u011fil, versiyon numaran\u0131zdan, g\u00fcncelleme zaman\u0131ndan veya veritaban\u0131 sat\u0131rlar\u0131n\u0131n checksumlar\u0131ndan da t\u00fcretebilirsiniz. \u00d6nemli olan, i\u00e7erik de\u011fi\u015fti\u011finde ETagin de de\u011fi\u015fmesini sa\u011flamak.<\/p>\n<p>Laravel prod ortam optimizasyonu ile HTTP cachei birlikte d\u00fc\u015f\u00fcnmek isterseniz, <a href='https:\/\/www.dchost.com\/blog\/laravel-uretim-optimizasyonu\/'>Laravel prod ortam optimizasyon rehberi<\/a> bu yaz\u0131n\u0131n iyi bir tamamlay\u0131c\u0131s\u0131 olacakt\u0131r.<\/p>\n<h2><span id=\"SPA_Projeleri_React_Vue_Angular_Icin_Onbellek_Kurallari\">SPA Projeleri (React, Vue, Angular) \u0130\u00e7in \u00d6nbellek Kurallar\u0131<\/span><\/h2>\n<p>SPA d\u00fcnyas\u0131nda \u00f6nbellekleme stratejisi WordPress veya klasik Laravel uygulamalar\u0131ndan biraz farkl\u0131. \u00c7\u00fcnk\u00fc \u00e7o\u011fu zaman tek bir index.html dosyas\u0131 ve onun referans verdi\u011fi b\u00fcy\u00fck JS ve CSS bundlelar\u0131 \u00fczerinden \u00e7al\u0131\u015f\u0131yorsunuz. Ayr\u0131ca API istekleri genelde ayr\u0131 bir origin veya alt yol \u00fczerinden servis ediliyor.<\/p>\n<h3><span id=\"indexhtml_icin_kisa_sureli_fakat_kontrollu_cache\">index.html i\u00e7in k\u0131sa s\u00fcreli fakat kontroll\u00fc cache<\/span><\/h3>\n<p>SPA projelerinde index.html, uygulaman\u0131z\u0131n giri\u015f noktas\u0131 ve \u00e7o\u011fu zaman \u00e7ok k\u00fc\u00e7\u00fck bir dosya. Bu dosyan\u0131n agresif \u015fekilde cachelenmesi, yeni deploylardan sonra kullan\u0131c\u0131lara eski versiyonun kalmas\u0131n\u0131 sa\u011flar. Bu y\u00fczden genelde \u015fu yakla\u015f\u0131m tercih edilir:<\/p>\n<ul>\n<li>Cache-Control no-cache veya max-age=60 gibi k\u0131sa bir s\u00fcre<\/li>\n<li>ETag veya Last-Modified ile ko\u015fullu istek deste\u011fi<\/li>\n<li>CDN taraf\u0131nda HTML cachei devre d\u0131\u015f\u0131 b\u0131rakmak veya \u00e7ok k\u0131sa tutmak<\/li>\n<\/ul>\n<p>no-cache kullan\u0131ld\u0131\u011f\u0131nda saklanan index.html yeniden kullan\u0131lmadan \u00f6nce do\u011frulan\u0131r. max-age=60 se\u00e7ildi\u011finde ise hen\u00fcz taze olan eski kopya yakla\u015f\u0131k bir dakikaya kadar kullan\u0131labilir. Yeni JS dosyalar\u0131na ge\u00e7i\u015f, g\u00fcncel index.html al\u0131nd\u0131\u011f\u0131nda ger\u00e7ekle\u015fir; a\u00e7\u0131k bir sekme kendili\u011finden yenilenmez. G\u00fcncel HTML ile yeni varl\u0131klar\u0131 birlikte yay\u0131mlay\u0131n; \u00f6nbellekteki HTML veya a\u00e7\u0131k sekmeler eski dosyalara ba\u015fvurabildi\u011fi s\u00fcrece \u00f6nceki varl\u0131k s\u00fcr\u00fcmlerini de eri\u015filebilir tutun. Bu, sonradan y\u00fcklenen JS par\u00e7alar\u0131 i\u00e7in de gereklidir.<\/p>\n<h3><span id=\"Hashli_JS_ve_CSS_dosyalari_icin_agresif_cache\">Hashli JS ve CSS dosyalar\u0131 i\u00e7in agresif cache<\/span><\/h3>\n<p>Build s\u00fcrecinde \u00fcretilen app.7c3f9a2d.js veya vendor.19b5c811.css gibi hashli dosyalar i\u00e7in tam tersine, m\u00fcmk\u00fcn olan en agresif cache politikas\u0131n\u0131 uygulamal\u0131s\u0131n\u0131z:<\/p>\n<ul>\n<li>Cache-Control public, max-age=31536000, immutable<\/li>\n<li>CDN seviyesinde de ayn\u0131 veya daha uzun s\u00fcre<\/li>\n<li>Versiyon de\u011fi\u015fikli\u011fini sadece dosya ismine b\u0131rakarak cache busting sa\u011flamak<\/li>\n<\/ul>\n<p>Dosyalar \u00f6nbellekte kald\u0131\u011f\u0131 ve hashleri de\u011fi\u015fmedi\u011fi s\u00fcrece tekrar ziyaretlerde b\u00fcy\u00fck JS dosyalar\u0131n\u0131n yeniden indirilmesi \u00f6nlenebilir. Yeni s\u00fcr\u00fcmde de\u011fi\u015fen dosyalar yeniden al\u0131n\u0131r. Bu yakla\u015f\u0131m HTML yan\u0131t\u0131n\u0131n TTFB&#8217;sini do\u011frudan azaltmaz; FCP ve LCP \u00fczerindeki kazan\u0131m, bu dosyalar\u0131n y\u00fckleme yolundaki rol\u00fcne ba\u011fl\u0131d\u0131r.<\/p>\n<h3><span id=\"Service_Worker_offline_cache_ve_CDN_uyumu\">Service Worker, offline cache ve CDN uyumu<\/span><\/h3>\n<p>E\u011fer PWA \u00f6zellikleri kullan\u0131yor ve service worker ile offline cache yap\u0131yorsan\u0131z, HTTP seviyesindeki Cache-Control kurallar\u0131n\u0131zla \u00e7ak\u0131\u015fmayacak bir mimari kurman\u0131z gerekir. Service worker\u0131n Cache API \u00fczerinden y\u00f6netti\u011fi kay\u0131tlar i\u00e7in HTTP ba\u015fl\u0131klar\u0131 tek ba\u015f\u0131na saklama ve silme politikas\u0131 olu\u015fturmaz; kullan\u0131c\u0131ya \u00f6zel yan\u0131tlar\u0131n kaydedilmemesi ve eski s\u00fcr\u00fcmlerin temizlenmesi worker mant\u0131\u011f\u0131nda da ele al\u0131nmal\u0131d\u0131r. Genel \u00f6neri \u015fu \u015fekildedir:<\/p>\n<ul>\n<li>Service worker scripti ve manifest dosyas\u0131 i\u00e7in k\u0131sa s\u00fcreli cache ve ETag<\/li>\n<li>Service worker\u0131n network-first, cache-first veya stale-while-revalidate stratejilerini bilin\u00e7li se\u00e7mek<\/li>\n<li>CDN taraf\u0131nda HTML ve service worker i\u00e7in cache bypass kurallar\u0131 tan\u0131mlamak<\/li>\n<\/ul>\n<p>SPA projelerini ayn\u0131 alan ad\u0131nda API ile birlikte yay\u0131nlama konusu da cache davran\u0131\u015f\u0131n\u0131 etkiler. Bu senaryoyu daha detayl\u0131 anlatt\u0131\u011f\u0131m\u0131z <a href='https:\/\/www.dchost.com\/blog\/react-vue-ve-angular-single-page-applicationlari-ayni-alan-adinda-api\/'>React, Vue ve Angular SPAleri ayn\u0131 alan ad\u0131nda API ile host etme rehberinde<\/a> Nginx y\u00f6nlendirme ve SSL mimarisine ek olarak, cache key ve path bazl\u0131 kurallara da de\u011finmi\u015ftik.<\/p>\n<h2><span id=\"CDN_ile_Origin_Onbellegini_Uyumlu_Hale_Getirmek\">CDN ile Origin \u00d6nbelle\u011fini Uyumlu Hale Getirmek<\/span><\/h2>\n<p>Taray\u0131c\u0131 ve CDN \u00f6nbelle\u011fi \u00e7o\u011fu zaman ayn\u0131 Cache-Control ba\u015fl\u0131klar\u0131na baksa da, davran\u0131\u015flar\u0131 ve \u00f6ncelikleri farkl\u0131d\u0131r. Origin sunucunuzda g\u00fczel ayarlar yap\u0131p CDN d\u00fczeyinde bunlar\u0131 yanl\u0131\u015f override ederseniz, \u00e7ok kafa kar\u0131\u015ft\u0131r\u0131c\u0131 sonu\u00e7larla kar\u015f\u0131la\u015fabilirsiniz.<\/p>\n<h3><span id=\"Cache_key_cookie_ve_Vary_basliklari\">Cache key, cookie ve Vary ba\u015fl\u0131klar\u0131<\/span><\/h3>\n<p>CDNlerin hangi iste\u011fi hangi cache girdisi ile e\u015fle\u015ftirece\u011fini belirleyen \u015fey cache keydir. Tipik olarak \u015fu par\u00e7alar\u0131 i\u00e7erir:<\/p>\n<ul>\n<li>Host (alan ad\u0131)<\/li>\n<li>Path (istek yolu)<\/li>\n<li>Sorgu parametreleri (query string) \u2013 hepsi veya se\u00e7ili olanlar<\/li>\n<li>Yap\u0131land\u0131rmaya g\u00f6re baz\u0131 headerlar (\u00f6rne\u011fin Accept-Encoding); Authorization de\u011ferinin varsay\u0131lan olarak anahtara kat\u0131ld\u0131\u011f\u0131n\u0131 varsaymay\u0131n<\/li>\n<\/ul>\n<p>WordPress ve WooCommerce sitelerinde en kritik nokta, kullan\u0131c\u0131ya \u00f6zel yan\u0131tlar\u0131n ortak \u00f6nbelle\u011fe girmemesidir. Genellikle login olmu\u015f kullan\u0131c\u0131lar\u0131 ve sepet i\u00e7eren oturumlar\u0131 cache d\u0131\u015f\u0131nda b\u0131rakmak i\u00e7in, belirli cookie adlar\u0131na g\u00f6re bypass kurallar\u0131 yaz\u0131l\u0131r. \u00d6rne\u011fin:<\/p>\n<ul>\n<li>Varsay\u0131lan wordpress_logged_in_ \u00f6nekiyle ba\u015flayan oturum \u00e7erezi varsa HTML cache bypass; LOGGED_IN_COOKIE \u00f6zelle\u015ftirildiyse ger\u00e7ek ad\u0131 kontrol edin<\/li>\n<li>woocommerce_cart_hash veya woocommerce_items_in_cart varsa cache bypass<\/li>\n<li>Bu adlar tam bir istisna listesi de\u011fildir. Di\u011fer oturum \u00e7erezlerini, ma\u011fazaya \u00f6zel sepet\/\u00f6deme\/hesap yollar\u0131n\u0131, dinamik\/API u\u00e7 noktalar\u0131n\u0131 ve sepet veya oturum durumunu de\u011fi\u015ftiren sorgu parametreli istekleri de de\u011ferlendirin.<\/li>\n<li>Hem origin tam sayfa \u00f6nbelle\u011finde hem CDN&#8217;de bypass, saklanm\u0131\u015f yan\u0131t\u0131n kullan\u0131m\u0131n\u0131 ve ki\u015fiselle\u015ftirilmi\u015f yan\u0131t\u0131n saklanmas\u0131n\u0131 engellemelidir. Oturum olu\u015fturan yan\u0131tlar\u0131 da ortak \u00f6nbelle\u011fe almay\u0131n ve bunlara public HTML politikas\u0131n\u0131 uygulamay\u0131n.<\/li>\n<\/ul>\n<p>Benzer \u015fekilde, Laravel tabanl\u0131 bir SaaS uygulamas\u0131nda Authorization header\u0131 i\u00e7eren isteklerin CDN seviyesinde cachelenmemesini istersiniz. Kullan\u0131c\u0131ya \u00f6zel yan\u0131tlar i\u00e7in private veya no-store politikas\u0131 ve Authorization i\u00e7eren istekler i\u00e7in CDN bypass kural\u0131 kullanabilirsiniz. Vary: Authorization tek ba\u015f\u0131na \u00f6nbelle\u011fe almay\u0131 engellemez.<\/p>\n<h3><span id=\"Origin_ve_CDN_arasinda_rol_dagilimi\">Origin ve CDN aras\u0131nda rol da\u011f\u0131l\u0131m\u0131<\/span><\/h3>\n<p>DCHost ortam\u0131nda tipik olarak \u015fu rol da\u011f\u0131l\u0131m\u0131n\u0131 \u00f6neriyoruz:<\/p>\n<ul>\n<li><strong>Origin (Nginx, Apache veya uygulama)<\/strong>: Do\u011fru Cache-Control, ETag, Last-Modified ve Vary ba\u015fl\u0131klar\u0131n\u0131 \u00fcretir. Statik dosyalar i\u00e7in uzun s\u00fcreli, HTML ve API i\u00e7in daha kontroll\u00fc s\u00fcreler belirler.<\/li>\n<li><strong>CDN<\/strong>: Origin ba\u015fl\u0131klar\u0131n\u0131 dikkate alacak \u015fekilde yap\u0131land\u0131r\u0131lmal\u0131; desteklenen ba\u015fl\u0131klar ve bunlar\u0131 ge\u00e7ersiz k\u0131lan edge kurallar\u0131 kontrol edilmelidir. Kritik yollar i\u00e7in ayr\u0131ca \u00f6nbellek istisnalar\u0131 tan\u0131mlan\u0131r. \u00d6rne\u011fin wp-admin alt\u0131ndaki t\u00fcm yollar\u0131 kesinlikle cachelememek, login ve checkout sayfalar\u0131n\u0131 HTML cache d\u0131\u015f\u0131nda b\u0131rakmak gibi.<\/li>\n<\/ul>\n<p>CDN se\u00e7imi ve maliyet optimizasyonu taraf\u0131nda daha derin bir bak\u0131\u015fa ihtiyac\u0131n\u0131z varsa, <a href='https:\/\/www.dchost.com\/blog\/cdn-trafik-maliyetlerini-dusurme\/'>CDN trafik maliyetlerini kontrol alt\u0131na alma rehberinde<\/a> origin pull, cache hit oran\u0131 ve b\u00f6lgesel fiyatland\u0131rma konular\u0131n\u0131 detayl\u0131 ele alm\u0131\u015ft\u0131k. Oradaki \u00f6nerileri, bu yaz\u0131daki HTTP \u00f6nbellek stratejisi ile birle\u015ftirdi\u011finizde hem performans hem de fatura taraf\u0131nda dengeli bir yap\u0131 kurabilirsiniz.<\/p>\n<h2><span id=\"Ornek_Onbellekleme_Senaryolari_WordPress_Laravel_API_ve_SPA\">\u00d6rnek \u00d6nbellekleme Senaryolar\u0131: WordPress, Laravel API ve SPA<\/span><\/h2>\n<p>\u00dc\u00e7 \u00f6rnek senaryoyu, i\u00e7erik t\u00fcr\u00fcne g\u00f6re uyarlanabilecek \u00f6nbellek kurallar\u0131 ile \u00f6zetleyelim.<\/p>\n<h3><span id=\"1_Klasik_blog_veya_kurumsal_WordPress_sitesi\">1. Klasik blog veya kurumsal WordPress sitesi<\/span><\/h3>\n<ul>\n<li>\u0130\u00e7eri\u011fi de\u011fi\u015fti\u011finde URL&#8217;si de de\u011fi\u015fen, herkese a\u00e7\u0131k statik varl\u0131klar (wp-content, wp-includes alt\u0131ndaki css, js, img, fonts): public, max-age=2592000 veya 31536000, immutable. Ayn\u0131 URL alt\u0131nda g\u00fcncellenen dosyalara bu uzun s\u00fcreli kural\u0131 uygulamay\u0131n.<\/li>\n<li>Anonim ziyaret\u00e7ilere ayn\u0131 i\u00e7eri\u011fi sunan HTML sayfalar (ana sayfa, yaz\u0131, kategori): sunucu taraf\u0131nda tam sayfa cache 60\u2013300 saniye, taray\u0131c\u0131 taraf\u0131nda k\u0131sa max-age (60\u2013120 saniye) veya no-cache. Oturum a\u00e7m\u0131\u015f kullan\u0131c\u0131lara \u00f6zel yan\u0131tlar\u0131 ve varsa sepet, \u00f6deme, hesap sayfalar\u0131n\u0131 tam sayfa ve CDN \u00f6nbelle\u011finden hari\u00e7 tutun.<\/li>\n<li>Y\u00f6netim paneli, wp-admin ve wp-login.php: no-store, no-cache, Pragma no-cache ve CDN seviyesinde cache bypass<\/li>\n<\/ul>\n<h3><span id=\"2_Laravel_tabanli_API_admin_panel\">2. Laravel tabanl\u0131 API + admin panel<\/span><\/h3>\n<ul>\n<li>\u0130\u00e7erik hashli URL&#8217;lerle sunulan, herkese a\u00e7\u0131k statik assetler (build klas\u00f6r\u00fc): public, max-age=31536000, immutable<\/li>\n<li>Herkese ayn\u0131 yan\u0131t\u0131 d\u00f6nd\u00fcren genel GET u\u00e7 noktalar\u0131 (\u00fcr\u00fcn listeleri, sabit i\u00e7erikler): public; max-age i\u00e7in 60\u2013300 saniye aral\u0131\u011f\u0131ndan uygun bir s\u00fcre se\u00e7imi ve ETag ile ko\u015fullu isteklerde 304 deste\u011fi<\/li>\n<li>Auth gerektiren GET u\u00e7 noktalar\u0131: hassas yan\u0131tlar i\u00e7in private, no-store. Hassas olmayan ve taray\u0131c\u0131da saklanmas\u0131na izin verilen yan\u0131tlar i\u00e7in ayr\u0131 bir se\u00e7enek olarak private ve k\u0131sa max-age<\/li>\n<li>Admin panelin kullan\u0131c\u0131ya \u00f6zel HTML ve JS yan\u0131tlar\u0131: private, no-store; CDN&#8217;de sunuluyorsa ilgili yollar i\u00e7in cache bypass. Herkese a\u00e7\u0131k, i\u00e7erik hashli ortak JS dosyalar\u0131 statik asset kural\u0131n\u0131 izleyebilir.<\/li>\n<\/ul>\n<h3><span id=\"3_SPA_frontend_ayri_API_sunucusu\">3. SPA frontend + ayr\u0131 API sunucusu<\/span><\/h3>\n<ul>\n<li>index.html: no-cache veya max-age=60, ETag deste\u011fi<\/li>\n<li>Hashli JS, CSS, font ve imajlar: public, max-age=31536000, immutable<\/li>\n<li>API GET u\u00e7 noktalar\u0131: herkese ayn\u0131 yan\u0131t\u0131 d\u00f6nd\u00fcren i\u00e7erikler i\u00e7in k\u0131sa s\u00fcreli public cache; taray\u0131c\u0131da saklanmas\u0131na izin verilen kullan\u0131c\u0131ya \u00f6zel yan\u0131tlar i\u00e7in private + ETag<\/li>\n<li>Login ve saklanmamas\u0131 gereken hassas kullan\u0131c\u0131 verilerini d\u00f6nen u\u00e7 noktalar: no-store ve CDN cache bypass<\/li>\n<\/ul>\n<p>Bu senaryolar\u0131n tamam\u0131nda ortak nokta \u015fu: \u00d6nbellekleme stratejisi sadece bir header eklemekten ibaret de\u011fil. Uygulama katman\u0131, web sunucusu, CDN ve taray\u0131c\u0131 birlikte d\u00fc\u015f\u00fcn\u00fcl\u00fcyor. Yeni bir proje g\u00f6\u00e7\u00fc veya kapasite planlamas\u0131nda bu d\u00f6rt katman\u0131n kurallar\u0131 birlikte de\u011ferlendirilmelidir.<\/p>\n<h2><span id=\"Sonuc_HTTP_Onbellegi_Dogru_Kuruldugunda_Ne_Kazanirsiniz\">Sonu\u00e7: HTTP \u00d6nbelle\u011fi Do\u011fru Kuruldu\u011funda Ne Kazan\u0131rs\u0131n\u0131z<\/span><\/h2>\n<p>HTTP Cache-Control ba\u015fl\u0131klar\u0131, ETag ve CDN \u00f6nbellek kurallar\u0131 do\u011fru kurguland\u0131\u011f\u0131nda kullan\u0131c\u0131lar\u0131n bekleme s\u00fcresi, sunucu kaynak kullan\u0131m\u0131 ve altyap\u0131 maliyeti azalabilir. Kazan\u0131m\u0131n b\u00fcy\u00fckl\u00fc\u011f\u00fc \u00f6nbellek isabet oran\u0131na, i\u00e7erik t\u00fcr\u00fcne, trafik da\u011f\u0131l\u0131m\u0131na ve fiyatland\u0131rmaya ba\u011fl\u0131d\u0131r. WordPress taraf\u0131nda s\u00fcr\u00fcmlenmi\u015f statik varl\u0131klar\u0131 uzun s\u00fcreli cacheleyip anonim ziyaret\u00e7ilere sunulan HTML i\u00e7in tam sayfa cache kurmak, ayn\u0131 donan\u0131m\u0131n kar\u015f\u0131layabildi\u011fi trafi\u011fi art\u0131rabilir. Laravel ve SPA projelerinde ise hashli assetler i\u00e7in agresif cache, index.html ve API cevaplar\u0131 i\u00e7in dengeli bir stratejiyle birle\u015fti\u011finde, yeni deploylarda i\u00e7erik g\u00fcncelli\u011fini korumaya ve pik trafikte origin y\u00fck\u00fcn\u00fc azaltmaya yard\u0131mc\u0131 olabilir.<\/p>\n<p>Buradan sonra atabilece\u011finiz en mant\u0131kl\u0131 ad\u0131m, mevcut sitenizin HTTP ba\u015fl\u0131klar\u0131n\u0131 ve CDN kurallar\u0131n\u0131 g\u00f6zden ge\u00e7irmek. Taray\u0131c\u0131 taraf\u0131nda hangi dosya ne kadar s\u00fcre cacheleniyor, CDN katman\u0131nda hangi pathler HTML cacheleniyor, login veya \u00f6deme sayfalar\u0131 g\u00fcvenli mi; hepsini tek tek kontrol edin. Altyap\u0131 se\u00e7erken <a href=\"https:\/\/www.dchost.com\/tr\/vps\">VPS<\/a> ve <a href=\"https:\/\/www.dchost.com\/tr\/fiziksel-sunucu\">dedicated sunucu<\/a> se\u00e7eneklerini kaynak kapasitesi, trafik \u00fccretleri ve web sunucusu ayarlar\u0131 \u00fczerindeki kontrol a\u00e7\u0131s\u0131ndan de\u011ferlendirin. Se\u00e7ilen planda HTTP ba\u015fl\u0131klar\u0131n\u0131 ve CDN kurallar\u0131n\u0131 kimin y\u00f6netece\u011fini netle\u015ftirin.<\/p>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>Taray\u0131c\u0131, CDN ve origin \u00f6nbelle\u011fini birlikte planlay\u0131n. WordPress, Laravel ve SPA \u00f6rnekleriyle saklama s\u00fcrelerini, ETag do\u011frulamas\u0131n\u0131 ve kullan\u0131c\u0131ya \u00f6zel yan\u0131tlar\u0131n \u00f6nbellek istisnalar\u0131n\u0131 inceleyin.<\/p>\n","protected":false},"author":1,"featured_media":12303,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[26],"tags":[],"class_list":["post-3574","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-teknoloji"],"_links":{"self":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts\/3574","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/comments?post=3574"}],"version-history":[{"count":7,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts\/3574\/revisions"}],"predecessor-version":[{"id":12305,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts\/3574\/revisions\/12305"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media\/12303"}],"wp:attachment":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media?parent=3574"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/categories?post=3574"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/tags?post=3574"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}