On Friday, June 19, 2015 at 12:14:10 PM UTC-4, Thomas Heller wrote:
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
Sounds like your URLs could use some cache busting. :) Then you can add far
future Expires headers, with no worries that users are seeing stale files.
Optimus is one way to inject some front-end performance in your
Ring-app. https://github.com/magnars/optimus
On Friday, June 19, 2015 at
None of this is applicable for closed intranet sites, and cache-control solves
the very annoying situation where users are running an old version of CSS or
Javascript.
I agree with these points for public facing ‘web sites’. For ‘enterprise SPAs’
there is usually a different context and set of
It is worth mentioning for others that if you are using
ring.middleware.defaults/wrap-defaults then this middleware is already in play.
On 19 Jun 2015, at 10:53, James Reeves ja...@booleanknot.com wrote:
Ring doesn't set any caching headers unless you add in middleware to do so.
The most
On Friday, June 19, 2015 at 5:54:03 AM UTC-4, James Reeves wrote:
Ring doesn't set any caching headers unless you add in middleware to do so.
The most common middleware is wrap-not-modified, which returns a 304
response if the etag or last-modified dates indicate the resource hasn't
been
Ring doesn't set any caching headers unless you add in middleware to do so.
The most common middleware is wrap-not-modified, which returns a 304
response if the etag or last-modified dates indicate the resource hasn't
been modified. For resources in jar files, the last-modified date is set to
the
Thanks James.
On 19 Jun 2015, at 10:53, James Reeves ja...@booleanknot.com wrote:
Ring doesn't set any caching headers unless you add in middleware to do so.
The most common middleware is wrap-not-modified, which returns a 304 response
if the etag or last-modified dates indicate the
Hi all, is there a quick way to disable caching for everything or
alternatively hash based on the contents of the resource. I am talking
specifically about CSS and javascript issues served from the JAR's class
path?
--
You received this message because you are subscribed to the Google
Groups
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
