You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since you are using such far-future expires headers for caching in the .htaccess file should you not be using a format to version your css and javascript files.
Such as the "script.js?v=1.0" or similar example in the .htaccess file
The text was updated successfully, but these errors were encountered:
I don't understand.... Since we're setting farfuture expires, we have to version at the filename level.. unless you expect to never modify these files at all.
I'm suggesting that we add it to the index.html template, so that future designers already have it in. Say we start with "?v=0.1" to the end of the js and css files referenced in the index.html template.
Since you are using such far-future expires headers for caching in the .htaccess file should you not be using a format to version your css and javascript files.
Such as the "script.js?v=1.0" or similar example in the .htaccess file
The text was updated successfully, but these errors were encountered: