Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Do not invalidate renderer caches when NO cache_buster is given #158
I think absence of "cache_buster" parameter will currently invalidate existing caches where cache_buster != 0.
The correct behaviour would be to pick whatever cache is available in those cases.
NOTE: when used in conjunction with Windshaft-CartoDB, the cache_buster is ALWAYS given with MULTILAYER endpoints (unified map api), while it depends on the user for legacy endpoints (inline map, table map).