a couple of questions for me to grasp the concept:
should i set expire headers for images to far future even if i might be edit them (optimize, resize or whatever) next week?
what about css files? i usually have to change something in those, probably more likely than the images.
what's about 'the filename has to be changed every time u edit them'?
otherwise the cached image will show instead?
kinda sucks to change the filename inside code all the time if they're used in a lot of places, no?
i'm not going after SEO stuff though. more like a 'best practices' approach. heard about the headers from paul irish in his html5boilerplate walkthrough video.
a couple of questions for me to grasp the concept:
should i set expire headers for images to far future even if i might be edit them (optimize, resize or whatever) next week?
what about css files? i usually have to change something in those, probably more likely than the images.
what's about 'the filename has to be changed every time u edit them'? otherwise the cached image will show instead? kinda sucks to change the filename inside code all the time if they're used in a lot of places, no?
This might be of interest: http://www.seomoz.org/ugc/expires-headers-for-seo-why-you-should-think-twice-before-using-them
one could say that i have a problem with static components being somewhat dynamic... ;)
cheers, paulie!
i'm not going after SEO stuff though. more like a 'best practices' approach. heard about the headers from paul irish in his html5boilerplate walkthrough video.