9 Aral\u0131k 2024 Pazartesi<\/p>\n
\nL\u00fctfen \u00f6nbelle\u011fe almam\u0131za izin verin.\n<\/p>\n
\n \u0130nternet y\u0131llar i\u00e7inde b\u00fcy\u00fcd\u00fck\u00e7e, Google’\u0131n tarama hacmi de artt\u0131. Google’\u0131n tarama altyap\u0131s\u0131 bulu\u015fsal \u00f6nbellekleme mekanizmalar\u0131n\u0131 desteklese de (asl\u0131nda her zaman desteklemi\u015ftir), yerel \u00f6nbelleklerden d\u00f6nd\u00fcr\u00fclebilen isteklerin say\u0131s\u0131 azalm\u0131\u015ft\u0131r: 10 y\u0131l \u00f6nce toplam getirilen verilerin yakla\u015f\u0131k %0,026’s\u0131 \u00f6nbelle\u011fe al\u0131nabilirdi ki bu zaten \u00e7ok etkileyici bir oran de\u011fildi; bug\u00fcn bu say\u0131 %0,017’dir.\n<\/p>\n
\n \u00d6nbellekleme, internet denilen b\u00fcy\u00fck yapbozun kritik bir par\u00e7as\u0131d\u0131r. \u00d6nbellekleme, sayfalar\u0131n tekrar ziyaret edildi\u011finde \u0131\u015f\u0131k h\u0131z\u0131nda y\u00fcklenmesini sa\u011flar, bilgi i\u015flem kaynaklar\u0131ndan ve dolay\u0131s\u0131yla do\u011fal kaynaklardan tasarruf sa\u011flar ve hem istemciler hem de sunucular i\u00e7in muazzam miktarda pahal\u0131 bant geni\u015fli\u011fi tasarrufu sa\u011flar.\n<\/p>\n
\n \u00d6zellikle bireysel URL’ler alt\u0131nda nadiren de\u011fi\u015fen i\u00e7eri\u011fe sahip b\u00fcy\u00fck bir siteniz varsa, yerel olarak \u00f6nbelle\u011fe almaya izin vermek sitenizin daha verimli taranmas\u0131na yard\u0131mc\u0131 olabilir. Google’\u0131n tarama altyap\u0131s\u0131, a\u015fa\u011f\u0131da tan\u0131mlanan bulu\u015fsal HTTP \u00f6nbelleklemesini destekler: \n \u015eiddetle \n \u0130stemcilerin \u00f6nbelleklerini yenilemesini gerektiren bir de\u011fi\u015fiklik olarak neyi kabul etti\u011finiz size kalm\u0131\u015f. \u00d6nerimiz, i\u00e7eri\u011finizde \u00f6nemli de\u011fi\u015fiklikler oldu\u011funda bir \u00f6nbellek yenilemesi istemenizdir; e\u011fer sadece sayfan\u0131z\u0131n alt\u0131ndaki telif hakk\u0131 tarihini g\u00fcncellediyseniz, bu muhtemelen \u00f6nemli de\u011fildir.\n<\/p>\n \n Google’\u0131n taray\u0131c\u0131lar\u0131, \n \u00d6nbelleklemeyi destekleyen Google taray\u0131c\u0131lar\u0131, bu URL’nin \u00f6nceki bir taramas\u0131nda d\u00f6nd\u00fcr\u00fclen \n \u0130stemci taraf\u0131nda, kullan\u0131c\u0131n\u0131n taray\u0131c\u0131s\u0131 veya Googlebot gibi, o URL alt\u0131ndaki i\u00e7erik istemcinin dahili \u00f6nbelle\u011finden al\u0131n\u0131r. Herhangi bir veri aktar\u0131m\u0131 s\u00f6z konusu olmad\u0131\u011f\u0131 i\u00e7in bu i\u015flem \u0131\u015f\u0131k h\u0131z\u0131nda ger\u00e7ekle\u015fir, kullan\u0131c\u0131lar\u0131 mutlu eder ve potansiyel olarak onlar i\u00e7in de baz\u0131 kaynaklardan tasarruf sa\u011flar.\n<\/p>\n \n T\u0131pk\u0131 \n E\u011fer \n E\u011fer benim gibiyseniz, bulu\u015fsal \u00f6nbelleklemenin nas\u0131l \u00e7al\u0131\u015ft\u0131\u011f\u0131n\u0131 anlamak zor olabilir, ancak istek ve yan\u0131t zincirine dair bir \u00f6rnek g\u00f6stermek bana yard\u0131mc\u0131 oluyor. \u0130\u015fte nas\u0131l \u00e7al\u0131\u015fmas\u0131 gerekti\u011fini g\u00f6rselle\u015ftirmek i\u00e7in iki zincir: \n Kullan\u0131c\u0131lar\u0131n\u0131z\u0131 mutlu etmek ve belki de bar\u0131nd\u0131rma faturan\u0131zdan birka\u00e7 kuru\u015f tasarruf etmek istiyorsan\u0131z, bar\u0131nd\u0131rma veya CMS sa\u011flay\u0131c\u0131n\u0131zla ya da geli\u015ftiricilerinizle siteniz i\u00e7in HTTP \u00f6nbelleklemesini nas\u0131l etkinle\u015ftirece\u011finiz hakk\u0131nda konu\u015fun. Ba\u015fka bir \u015fey olmasa bile, kullan\u0131c\u0131lar\u0131n\u0131z sizi biraz daha sevecektir.\n<\/p>\n \n \u00d6nbellekleme hakk\u0131nda sohbet etmek isterseniz, size en yak\u0131n
\n HTTP \u00f6nbellekleme standard\u0131<\/a>, \u00f6zellikle ETag<\/code> yan\u0131t ve If-None-Match<\/code> istek ba\u015fl\u0131\u011f\u0131 ile Last-Modified<\/code> yan\u0131t ve If-Modified-Since<\/code> istek ba\u015fl\u0131\u011f\u0131 arac\u0131l\u0131\u011f\u0131yla.\n<\/p>\nETag<\/code> kullanman\u0131z\u0131 \u00f6neririz \u00e7\u00fcnk\u00fc hatalara ve yanl\u0131\u015fl\u0131klara daha az e\u011filimlidir (de\u011feri, Last-Modified<\/code> de\u011ferinin aksine yap\u0131land\u0131r\u0131lmam\u0131\u015ft\u0131r). Ve e\u011fer se\u00e7ene\u011finiz varsa, her ikisini de ayarlay\u0131n: internet size te\u015fekk\u00fcr edecektir. Belki.\n<\/p>\nETag<\/code> ve If-None-Match<\/code><\/h2>\nETag<\/code> tabanl\u0131 ko\u015fullu istekleri tam olarak
\n HTTP \u00f6nbellekleme standard\u0131<\/a>i\u00e7inde tan\u0131mland\u0131\u011f\u0131 gibi destekler. Yani, Google’\u0131n taray\u0131c\u0131lar\u0131na \u00f6nbellekleme tercihini bildirmek i\u00e7in Etag<\/code> de\u011ferini, eri\u015filen URL taraf\u0131ndan bar\u0131nd\u0131r\u0131lan i\u00e7eri\u011fin temsiline \u00f6zg\u00fc herhangi bir rastgele ASCII dizesine (genellikle i\u00e7eri\u011fin veya s\u00fcr\u00fcm numaras\u0131n\u0131n bir karmas\u0131, ancak \u03c0’nin bir par\u00e7as\u0131 da olabilir, size kalm\u0131\u015f) ayarlay\u0131n. \u00d6rne\u011fin, ayn\u0131 i\u00e7eri\u011fin farkl\u0131 s\u00fcr\u00fcmlerini ayn\u0131 URL alt\u0131nda bar\u0131nd\u0131r\u0131yorsan\u0131z (\u00f6rne\u011fin, mobil ve masa\u00fcst\u00fc s\u00fcr\u00fcm\u00fc), her s\u00fcr\u00fcm\u00fcn kendi benzersiz ETag<\/code> de\u011feri olabilir.\n<\/p>\nETag<\/code> de\u011ferini If-None-Match ba\u015fl\u0131\u011f\u0131nda<\/code>g\u00f6nderecektir. E\u011fer taray\u0131c\u0131 taraf\u0131ndan g\u00f6nderilen ETag<\/code>
\n de\u011feri, sunucunun olu\u015fturdu\u011fu mevcut de\u011ferle e\u015fle\u015firse, sunucunuz HTTP g\u00f6vdesi olmadan bir HTTP 304<\/code> (De\u011fi\u015ftirilmedi) durum kodu d\u00f6nd\u00fcrmelidir. Bu son k\u0131s\u0131m, yani HTTP g\u00f6vdesinin olmamas\u0131, birka\u00e7 nedenden dolay\u0131 \u00f6nemlidir:\n<\/p>\n\n
Last-Modified<\/code> ve If-Modified-Since<\/code><\/h2>\nETag<\/code>gibi, Google’\u0131n taray\u0131c\u0131lar\u0131 da Last-Modified tabanl\u0131<\/code>
\n ko\u015fullu istekleri, tam olarak HTTP \u00d6nbellekleme standard\u0131nda tan\u0131mland\u0131\u011f\u0131 gibi destekler. Bu, anlamsal a\u00e7\u0131dan ETag<\/code> ile ayn\u0131 \u015fekilde \u00e7al\u0131\u015f\u0131r (kayna\u011f\u0131n \u00f6nbelle\u011fe al\u0131n\u0131p al\u0131namayaca\u011f\u0131na karar vermek i\u00e7in bir tan\u0131mlay\u0131c\u0131 kullan\u0131l\u0131r) ve istemci taraf\u0131nda ETag<\/code> ile ayn\u0131 avantajlar\u0131 sa\u011flar.\n<\/p>\nLast-Modified<\/code> kullan\u0131yorsan\u0131z birka\u00e7 \u00f6nerimiz var:\n<\/p>\n\n
ba\u015fl\u0131\u011f\u0131ndaki tarih,<\/code> HTTP standard\u0131na
\n g\u00f6re bi\u00e7imlendirilmelidir<\/a>. Ayr\u0131\u015ft\u0131rma sorunlar\u0131n\u0131 \u00f6nlemek i\u00e7in a\u015fa\u011f\u0131daki tarih bi\u00e7imini kullanman\u0131z\u0131 \u00f6neririz: G\u00fcn, DD Ay YYYY SS:DD:SS<\/span> Saat Dilimi”. \u00d6rne\u011fin,Cum, 4 Eyl 1998 19:15:56 GMT<\/span>“.\n <\/li>\nmax-age<\/code> alan\u0131n\u0131
\n Cache-Control<\/code> ba\u015fl\u0131\u011f\u0131nda ayarlamay\u0131 d\u00fc\u015f\u00fcn\u00fcn; bu, taray\u0131c\u0131lar\u0131n belirli bir URL’yi ne zaman tekrar tarayacaklar\u0131n\u0131 belirlemelerine yard\u0131mc\u0131 olur. max-age<\/code> alan\u0131n\u0131n de\u011ferini, i\u00e7eri\u011fin de\u011fi\u015fmeden kalaca\u011f\u0131 beklenen saniye say\u0131s\u0131na ayarlay\u0131n. \u00d6rne\u011fin, Cache-Control: max-age=94043<\/code>.\n <\/li>\n<\/ol>\n\u00d6rnekler<\/h2>\n
ETag<\/code>\/If-None-Match<\/code> ve biri
\n Last-Modified<\/code>\/If-Modified-Since<\/code> i\u00e7in:\n<\/p>\n\n
\n <\/th>\n ETag<\/code>\/If-None-Match<\/code><\/th>\nLast-Modified<\/code>\/If-Modified-Since<\/code><\/th>\n<\/tr>\n\n \n Bir sunucunun taramaya yan\u0131t\u0131:<\/strong> Bu, bir taray\u0131c\u0131n\u0131n \u00f6n ko\u015ful ba\u015fl\u0131k alanlar\u0131n\u0131 kaydedebilece\u011fi yan\u0131tt\u0131r ETag<\/code> ve Last-Modified<\/code>.\n <\/td>\n\n \n \n \n Sonraki taray\u0131c\u0131 ko\u015fullu iste\u011fi:<\/strong> Ko\u015fullu istek, \u00f6nceki bir istekten kaydedilen \u00f6n ko\u015ful ba\u015fl\u0131k de\u011ferlerine dayan\u0131r. De\u011ferler, do\u011frulama i\u00e7in sunucuya If-None-Match<\/code> ve If-Modified-Since<\/code>
\n istek ba\u015fl\u0131klar\u0131nda geri g\u00f6nderilir.\n <\/td>\n\n \n \n \n Ko\u015fullu iste\u011fe sunucu yan\u0131t\u0131:<\/strong> Taray\u0131c\u0131 taraf\u0131ndan g\u00f6nderilen \u00f6n ko\u015ful ba\u015fl\u0131k de\u011ferleri sunucu taraf\u0131nda do\u011fruland\u0131\u011f\u0131ndan, sunucu taray\u0131c\u0131ya bir 304<\/code>
\n HTTP durum kodu (HTTP g\u00f6vdesi olmadan) d\u00f6nd\u00fcr\u00fcr. Bu, \u00f6n ko\u015fullar do\u011frulanana kadar (sunucu taraf\u0131nda ETag<\/code> veya
\n Last-Modified<\/code> tarihi de\u011fi\u015fene kadar) sonraki her istekte ger\u00e7ekle\u015fecektir.\n <\/td>\n\n \n
\n Search Central yard\u0131m toplulu\u011funa<\/a>gidin ve \u00f6nbelle\u011fe alma \u015feklimiz hakk\u0131nda yorumlar\u0131n\u0131z varsa,
\n \u00f6nbellekleme hakk\u0131ndaki belgelere<\/a>
\n bu blog yaz\u0131s\u0131yla birlikte yay\u0131nlad\u0131\u011f\u0131m\u0131z geri bildirimde bulunun.\n<\/p>\n