Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

REST Cache not recreated #271

Open
yfr opened this issue Oct 26, 2021 · 0 comments
Open

REST Cache not recreated #271

yfr opened this issue Oct 26, 2021 · 0 comments

Comments

@yfr
Copy link

yfr commented Oct 26, 2021

We are using MapCache with the Google Cloud Storage REST cache. We have set an auto_expire to 60 for example. This should recreate the requested tiles after 60 seconds. This does not work. The tiles are never recreated.

In the client, I see these response data. Cache-Control: max-age=60 is always 60.

Date: Tue, 26 Oct 2021 09:50:23 GMT
Server: Apache/2.4.25 (Debian)
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: POST, GET, OPTIONS
Cache-Control: max-age=60
Expires: Tue, 26 Oct 2021 09:51:23 GMT
Content-Length: 3079
Content-Type: image/png

For tests, I switched to a disk cache. There, the recreation works just fine, and the following response is given to the client.

Date: Tue, 26 Oct 2021 09:50:06 GMT
Server: Apache/2.4.25 (Debian)
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: POST, GET, OPTIONS
Last-Modified: Tue, 26 Oct 2021 09:50:07 GMT
Cache-Control: max-age=59
Expires: Tue, 26 Oct 2021 09:51:06 GMT
Content-Length: 3658
Content-Type: image/png

Cache-Control: max-age=60 will count down to the time to recreate the tile. Notice also the Last-Modified header, which is not present in the mapCache response with REST cache.

We are guessing that the Last-Modified from the REST API is not used. Can someone help here? Do we need to add something special to the REST cache config?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant