Explanation for expires header
Posted
by sushil bharwani
on Stack Overflow
See other posts from Stack Overflow
or by sushil bharwani
Published on 2010-05-11T18:32:24Z
Indexed on
2010/05/11
18:34 UTC
Read the original article
Hit count: 338
I have a joomla application working on Apache.To improve site performace we have written a .htaccess file to root of the application with setting a far future expires header to all the static content. As desired first time the files load in fresh with 200 status code. when again click on the same link many of the files are served directly from cache. I need explanation for two things
When i press f5 then a number of files load with 304 status code however i expected them to be coming directly from cache without hitting the server for a status header?
- When i close the browser and come back to the same page again i see the same thing happening a number of files load with 304 status code although i thought they will load directly from the browser cache?
I understand that 304 also servs file from browser cache but i want to avoid the header communication between servers as my static files wont ever change. Also i want to add that my requests are over a https connection does that create any issue.
© Stack Overflow or respective owner