> > > Cache-control is evil. Users concerned with seeing the most up-to-date > information know to hit reload (and probably do anyway, just to be sure), > and there's also the option of AJAX polling for that (or whatever precisely > sites like Facebook do). > > I don't even .... a wrong Cache-Control will cause problems but Cache-Control is probably one of the most important headers to set for your webapp. It is also one of the harder ones to get right but the benefits are significant.
As for preventing users from seeing stale CSS/Javascript I'd recommend serving files with a unique name which changes with each new release. This way old HTML refers to old CSS and new HTML to new CSS, plus you can add "Cache-Control: public, max-age=31536000" to the static files which allows the browser to actually SKIP checking if a resource was modified (ie. huge speed gains, no if-modified-since->not modified round trip). Disabling cache is usually the least desirable option and if you care about performance at all you should think twice before doing so (yes, even for intranet sites). /thomas -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
