3 ms·
> Just like they already randomise asset filenames to avoid caching. But why? Isn't the whole point of caching to improve delivery if static assets? Did they
by xg15 7y ago
> Just like they already randomise asset filenames to avoid caching.
But why? Isn't the whole point of caching to improve delivery if static assets?
Did they run into staleness problems? Then why not use if-modified-since/if-none-match?
- noselasd 7y agoYou are assuming browsers(there are many more than chrome&ff) ,proxies, etc. do caching correctly.
- summm 7y agoAnd you are assuming web devs could configure their servers properly. Anyway, it all boils down to the mentality of lowest common denominator: using that workaround, nobody has any incentive to fix their proxy.