If a client uses the Cache-Control: no-cache header in the request, then we should skip the cache and render the tile fresh. We can store the freshly-generated tile in the cache for later use.
This could be useful in real life and for operations/debugging. It would also let us more easily test performance of uncached tiles without having to actually disable the cache. Since we would still store the rendered image/grid on S3, the app load would be more realistic, too.
If a client uses the
Cache-Control: no-cache
header in the request, then we should skip the cache and render the tile fresh. We can store the freshly-generated tile in the cache for later use.This could be useful in real life and for operations/debugging. It would also let us more easily test performance of uncached tiles without having to actually disable the cache. Since we would still store the rendered image/grid on S3, the app load would be more realistic, too.