Re: cache-busting and query-string versioning

>
> I do think that having to change the names of modified assets is a bit sad.
> Wouldn't it be nice if etag validators were enough? On the other hand, if a
> bug needs to be fixed in say "login.js", one would certainly want to
> propagate those changes instantaneously. As it is now, I can not have my
> pie and eat it :-(
>

If you want to avoid round-trips, version the URI
("login-20160628.js") and send Expires. If you want to keep the URI
("index.html"), send Last-Modified and ETag.

I don't think there can ever be a magic bullet (in 1.x, without server
push) to resolve this issue, and it's been known for long enough that
best practices and user expectations should be pretty well established
by now.

Cheers
-- 
  Matthew Kerwin
  http://matthew.kerwin.net.au/

Received on Monday, 27 June 2016 23:40:12 UTC