With an explicit version number in the URL, there's little reason to have a 10 minute expiration period for a .js file. Why not save bandwidth and money (and improve performance to boot) with a more reasonable expires setting?
This file integrates as a widget code on customer websites. We don't expect our customers to change this code often. However, we do continue to change the underlying code (to push updates, new releases etc). The idea is that visitors on our customer websites get the new code whenever it changes.
I do agree that the number (10mins) could be a bit scientific. But you get the idea as to why we kept it as such.
3 comments
[ 3.7 ms ] story [ 1147 ms ] threadI do agree that the number (10mins) could be a bit scientific. But you get the idea as to why we kept it as such.