On Wed, Nov 2, 2011 at 5:17 PM, Greg R. [email protected] wrote:
If you use Rails 3.1.1, it will by default add non-digested assets in
addition to the digest ones. So in static pages, you can just refer to the
non-digest asset filenames, and they should be consistent.
I currently have this snippet in my Apache sites-available file to
Far future expiration:
ExpiresDefault "access plus 1 week"
When using these non-digest asset filenames, I believe there is a risk
could be “frozen” on old versions.
Should the non-digest asset filenames not be marked in a special way or
stored in a
special directory to make it easier to exclude them from far future
Or is there an easy way to improve my configuration to only do far
on digested asset filenames?