http - Why digest are used in Rails 4 for static content instead of ETag -



http - Why digest are used in Rails 4 for static content instead of ETag -

i think http's etag mechanism invalidating stale cached content. , digests used same sake. why improve , why etags not enough?

because etags still require client nail server see if client's cached re-create still fresh. rails puts far future expires header on assets means client never nail server 1 time again asset, has cached. digests become means server create client new version of asset. think rails used utilize timestamps instead of digests, digests have added, little benefit if revert asset previous state, digest same, , client may still have cached.

ruby-on-rails http asset-pipeline etag

Comments

Popular posts from this blog

formatting - SAS SQL Datepart function returning odd values -

c++ - Apple Mach-O Linker Error(Duplicate Symbols For Architecture armv7) -

php - Yii 2: Unable to find a class into the extension 'yii2-admin' -