The following warnings occurred:
Warning [2] count(): Parameter must be an array or an object that implements Countable - Line: 802 - File: showthread.php PHP 7.2.10-0ubuntu0.18.04.1 (Linux)
File Line Function
/showthread.php 802 errorHandler->error



Current time: 12-14-2018, 06:54 AM Hello There, Guest! (LoginRegister)

Post Reply 
 
Thread Rating:
  • 1 Vote(s) - 5 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Long Expires/max-age dates, why its suggested?
10-15-2014, 01:15 AM (This post was last modified: 10-15-2014 01:18 AM by postcd.)
Post: #1
Brick Long Expires/max-age dates, why its suggested?
Hi, I found on many places people suggest having like 1 month or 1 year expiration dates on images. So browser cache it for long time..

BUT I would think its better to have image expiration time like 5 minutes. WHY? Because if i modiffy some image i want users to see modiffied image quickly, not have old image cached maybe weeks on their browser cache.. (i know i can change image name, but i not always want to rename it)

While i set 5 minutes expiry date, i believe after this time browser asks server if that image modiffication date changed (tru last-Modiffied or etag). If image mod. date not changed, then its again served from browser cache next 5 minutes? (is that so?) So no bandwidth/performance loss, but i know people will see fresh images..? Thank you
Find all posts by this user
Quote this message in a reply
Post Reply 


Messages In This Thread
Long Expires/max-age dates, why its suggested? - postcd - 10-15-2014 01:15 AM

Forum Jump:


User(s) browsing this thread: 1 Guest(s)