Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP

Loading…

Do not invalidate renderer caches when NO cache_buster is given #158

Closed
strk opened this Issue · 0 comments

1 participant

@strk

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).

@strk strk added the performance label
@strk strk added this to the 0.19.1 milestone
@strk strk added the enhancement label
@strk strk closed this in 4084c3f
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.