Revisioning Assets using <base>
One of the first performance optimization tricks you learn is setting a far-future cache expiration date. This prevents browsers from repeatedly fetching, even revalidating, static resources. The downside of this approach to reducing network overhead is that you need to change the resources' URLs in order to have a browser re-download it. This post covers the problems encountered when using
<base> to achieve exactly that.