I had no luck with features. Introducing HTTP cache relevant parameters directly (outside of the HTML doc) does without a doubt get the job done for me.   The headers in The solution furnished by BalusC won't stop Safari 5 (And perhaps more mature variations at the same time) from exh