{"id":2125,"date":"2026-05-22T09:09:58","date_gmt":"2026-05-22T06:09:58","guid":{"rendered":"https:\/\/allinonewpsettings.com\/blog\/?p=2125"},"modified":"2026-08-02T12:09:34","modified_gmt":"2026-08-02T12:09:34","slug":"wordpress-htaccess-ile-tarayici-onbellek-basliklari-nasil-eklenir","status":"publish","type":"post","link":"https:\/\/allinonewpsettings.com\/blog\/tr\/wordpress-htaccess-ile-tarayici-onbellek-basliklari-nasil-eklenir\/","title":{"rendered":"WordPress’te .htaccess ile Taray\u0131c\u0131 \u00d6nbellek Ba\u015fl\u0131klar\u0131 Nas\u0131l Eklenir?"},"content":{"rendered":"

Bir y\u0131ll\u0131k taray\u0131c\u0131 \u00f6nbelle\u011fi performans\u0131 iyile\u015ftirebilir; ancak ayn\u0131 kural s\u00fcr\u00fcmlenmeyen bir JavaScript dosyas\u0131na veya dinamik HTML’e uygulan\u0131rsa ziyaret\u00e7iler g\u00fcnlerce eski i\u00e7eri\u011fi g\u00f6rebilir. CDN’in ekledi\u011fi ikinci bir Cache-Control<\/code> ba\u015fl\u0131\u011f\u0131 da taray\u0131c\u0131ya hangi politikan\u0131n uygulanaca\u011f\u0131n\u0131 belirsiz h\u00e2le getirir.<\/p>\n

Bu rehber, WordPress’te taray\u0131c\u0131 \u00f6nbellek ba\u015fl\u0131klar\u0131n\u0131 .htaccess<\/code> \u00fczerinden g\u00fcvenli bi\u00e7imde planlamay\u0131 anlat\u0131r. Statik dosyalar ile dinamik yan\u0131tlar\u0131 nas\u0131l ay\u0131raca\u011f\u0131n\u0131z\u0131, uzun \u00f6nbellek s\u00fcresinin ne zaman g\u00fcvenli oldu\u011funu ve son yan\u0131t\u0131n ger\u00e7ekten hangi katmanda olu\u015fturuldu\u011funu nas\u0131l do\u011frulayaca\u011f\u0131n\u0131z\u0131 g\u00f6receksiniz.<\/p>\n

\n\u0130\u00e7indekiler<\/strong><\/p>\n
    \n
  1. Taray\u0131c\u0131 \u00f6nbellek ba\u015fl\u0131klar\u0131 nedir?<\/a><\/li>\n
  2. Ger\u00e7ek\u00e7i bir WordPress \u00f6rne\u011fi<\/a><\/li>\n
  3. Neden \u00f6nemlidir ve ne zaman kullan\u0131l\u0131r?<\/a><\/li>\n
  4. Yeni ba\u015flayanlar i\u00e7in g\u00fcvenli uygulama<\/a><\/li>\n
  5. \u0130leri teknik yakla\u015f\u0131m<\/a><\/li>\n
  6. Riskler, s\u0131k hatalar, yedek ve rollback<\/a><\/li>\n
  7. AIOWS Htaccess D\u00fczenleyici nas\u0131l yard\u0131mc\u0131 olur?<\/a><\/li>\n
  8. \u0130lgili AIOWS yaz\u0131lar\u0131<\/a><\/li>\n
  9. Sonu\u00e7 ve \u00f6nerilen yol<\/a><\/li>\n
  10. Resm\u00ee kaynaklar<\/a><\/li>\n<\/ol>\n<\/div>\n

    Taray\u0131c\u0131 \u00f6nbellek ba\u015fl\u0131klar\u0131 nedir?<\/h2>\n

    Taray\u0131c\u0131 \u00f6nbellek ba\u015fl\u0131klar\u0131, bir yan\u0131t\u0131n istemcide veya payla\u015f\u0131ml\u0131 \u00f6nbellekte ne kadar s\u00fcre saklanabilece\u011fini ve ne zaman yeniden do\u011frulanmas\u0131 gerekti\u011fini belirtir. Cache-Control<\/code> bu davran\u0131\u015f\u0131 max-age<\/code>, public<\/code>, private<\/code>, no-cache<\/code> ve immutable<\/code> gibi y\u00f6nergelerle tan\u0131mlar. Expires<\/code> ise sona erme zaman\u0131n\u0131 mutlak tarih olarak bildirir.<\/p>\n

    Uzun s\u00fcreli \u00f6nbellek, i\u00e7erik de\u011fi\u015fti\u011finde URL’si de de\u011fi\u015fen CSS, JavaScript, g\u00f6rsel ve font dosyalar\u0131nda etkilidir. WordPress sayfalar\u0131, oturum a\u00e7m\u0131\u015f kullan\u0131c\u0131lara verilen yan\u0131tlar, WooCommerce sepeti ve hesap ekranlar\u0131 ise ayn\u0131 politikaya uygun de\u011fildir. Bu i\u00e7erikler ki\u015fiye veya zamana g\u00f6re de\u011fi\u015febildi\u011finden daha k\u0131sa ve kontroll\u00fc bir \u00f6nbellek stratejisi ister.<\/p>\n

    Ger\u00e7ek\u00e7i bir WordPress \u00f6rne\u011fi<\/h2>\n

    Bir ekip, \u00f6rnek bir yap\u0131land\u0131rmadan ald\u0131\u011f\u0131 bir y\u0131ll\u0131k \u00f6nbellek s\u00fcresini t\u00fcm siteye uyguluyor. Yeni s\u00fcr\u00fcm yay\u0131mland\u0131\u011f\u0131nda app.js<\/code> dosyas\u0131n\u0131n URL’si de\u011fi\u015fmedi\u011fi i\u00e7in baz\u0131 ziyaret\u00e7iler eski JavaScript’i kullanmaya devam ediyor. Ayn\u0131 s\u0131rada CDN de kendi Cache-Control<\/code> ba\u015fl\u0131\u011f\u0131n\u0131 ekliyor ve origin ile ziyaret\u00e7inin g\u00f6rd\u00fc\u011f\u00fc yan\u0131t birbirinden ayr\u0131l\u0131yor.<\/p>\n

    Do\u011fru \u00e7\u00f6z\u00fcm, t\u00fcm dosyalara tek s\u00fcre vermek de\u011fildir. \u00d6nce statik dosyalar\u0131n her yay\u0131nda yeni bir s\u00fcr\u00fcm parametresi veya hash i\u00e7eren dosya ad\u0131 al\u0131p almad\u0131\u011f\u0131n\u0131 belirleyin. Ard\u0131ndan HTML ve kullan\u0131c\u0131ya \u00f6zel sayfalar\u0131 uzun \u00f6nbelle\u011fin d\u0131\u015f\u0131nda tutun. Son olarak origin, CDN ve taray\u0131c\u0131 yan\u0131tlar\u0131n\u0131 ayr\u0131 ayr\u0131 inceleyerek ziyaret\u00e7iye ula\u015fan tek ve tutarl\u0131 politikay\u0131 do\u011frulay\u0131n.<\/p>\n

    Neden \u00f6nemlidir ve ne zaman kullan\u0131l\u0131r?<\/h2>\n

    Do\u011fru taray\u0131c\u0131 \u00f6nbelle\u011fi, tekrar ziyaretlerde aktar\u0131lan veri miktar\u0131n\u0131 azalt\u0131r ve statik kaynaklar\u0131n daha h\u0131zl\u0131 y\u00fcklenmesini sa\u011flar. \u00d6zellikle de\u011fi\u015fmeyen tema dosyalar\u0131, fontlar ve s\u00fcr\u00fcmlenmi\u015f g\u00f6rseller i\u00e7in uzun s\u00fcreler gereksiz yeniden indirmeleri \u00f6nler.<\/p>\n

    Bununla birlikte \u00f6nbellek s\u00fcresi, yay\u0131n s\u00fcrecinden ba\u011f\u0131ms\u0131z d\u00fc\u015f\u00fcn\u00fclemez. Dosya i\u00e7eri\u011fi de\u011fi\u015fti\u011finde URL ayn\u0131 kal\u0131yorsa aylar s\u00fcren max-age<\/code> eski kodu ziyaret\u00e7inin taray\u0131c\u0131s\u0131nda kilitleyebilir. immutable<\/code> y\u00f6nergesi de yaln\u0131zca URL’nin i\u00e7erik de\u011fi\u015fti\u011finde kesin olarak yenilendi\u011fi dosyalarda kullan\u0131lmal\u0131d\u0131r. CDN veya optimizasyon eklentisi ba\u015fl\u0131klar\u0131 zaten y\u00f6netiyorsa .htaccess<\/code> i\u00e7ine ikinci bir politika eklemek yerine denetimi tek katmanda toplamak daha g\u00fcvenlidir.<\/p>\n

    Yeni ba\u015flayanlar i\u00e7in g\u00fcvenli uygulama<\/h2>\n
      \n
    1. CSS, JavaScript, g\u00f6rsel ve font URL’lerinin yay\u0131n s\u0131ras\u0131nda nas\u0131l s\u00fcr\u00fcmlendi\u011fini belirleyin. \u0130\u00e7erik de\u011fi\u015fti\u011finde URL de\u011fi\u015fmiyorsa \u00e7ok uzun \u00f6nbellek s\u00fcresi kullanmay\u0131n.<\/li>\n
    2. Taray\u0131c\u0131ya ula\u015fan mevcut Cache-Control<\/code> ve Expires<\/code> ba\u015fl\u0131klar\u0131n\u0131 inceleyin. Origin yan\u0131t\u0131n\u0131 CDN \u00fczerinden gelen yan\u0131tla kar\u015f\u0131la\u015ft\u0131r\u0131n.<\/li>\n
    3. Etkin .htaccess<\/code> dosyas\u0131n\u0131 yedekleyin ve hosting paneli ya da FTP \u00fczerinden dosyaya eri\u015fimi haz\u0131r tutun.<\/li>\n
    4. Kural\u0131 yaln\u0131zca uygun statik uzant\u0131larla s\u0131n\u0131rland\u0131r\u0131n. HTML, PHP \u00e7\u0131kt\u0131s\u0131, y\u00f6netim ekranlar\u0131, sepet ve hesap sayfalar\u0131n\u0131 uzun s\u00fcreli public<\/code> \u00f6nbelle\u011fe dahil etmeyin.<\/li>\n
    5. \u00d6nce k\u0131sa ve \u00f6l\u00e7\u00fcl\u00fc bir s\u00fcreyle deneyin. Ba\u015fl\u0131klar\u0131n tek kez g\u00f6nderildi\u011fini ve hedef dosya t\u00fcrlerinde beklendi\u011fi gibi de\u011fi\u015fti\u011fini do\u011frulay\u0131n.<\/li>\n
    6. Standart yay\u0131n s\u00fcreciyle zarars\u0131z bir CSS veya g\u00f6rsel de\u011fi\u015fikli\u011fi yap\u0131n. Yeni dosyan\u0131n ziyaret\u00e7iye ula\u015ft\u0131\u011f\u0131n\u0131, eski URL’nin ise belirlenen politika uyar\u0131nca davrand\u0131\u011f\u0131n\u0131 s\u0131nay\u0131n.<\/li>\n<\/ol>\n

      \u0130leri teknik yakla\u015f\u0131m<\/h2>\n

      \u0130leri incelemede yaln\u0131zca .htaccess<\/code> i\u00e7eri\u011fine bakmak yeterli de\u011fildir. Apache mod\u00fclleri, WordPress eklentileri, reverse proxy ve CDN ayn\u0131 yan\u0131ta ba\u015fl\u0131k ekleyebilir. Taray\u0131c\u0131ya ula\u015fan nihai yan\u0131t\u0131 belirlemek i\u00e7in origin adresini, ziyaret\u00e7iye a\u00e7\u0131k URL’yi ve m\u00fcmk\u00fcnse farkl\u0131 bir CDN noktas\u0131n\u0131 kar\u015f\u0131la\u015ft\u0131r\u0131n.<\/p>\n