I'm not sure if it's intentional or not, but at least with the default .htaccess configs, markerdata.js is serve with explicit "no-cache" headers. This can be bad for site performance, are there any plans to make this JS cacheable ?
I'm not sure if it's intentional or not, but at least with the default .htaccess configs, markerdata.js is serve with explicit "no-cache" headers. This can be bad for site performance, are there any plans to make this JS cacheable ?
Comments
Comment #1
bdragon commentedI believe this is fixed for good in the final, it was switched to create and use a physical file.