WebEngage is serving over 100 million widget requests per month
blog.webengage.com
blog.webengage.com
Cache-Control: private, max-age=600
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?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.