-
Notifications
You must be signed in to change notification settings - Fork 184
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
http caching could be improved #289
Comments
Thanks for the suggestion, we've gotten similar requests in the past though it's not entirely trivial in this case. The first hurdle is that map tiles for "today" and "yesterday" get frequently updated and we wouldn't want the browser to show a mish-mash of old and new tiles. The second is that, at least when we looked into it a few years ago, Worldview relies on "fresh" tiles for certain features. We'll plan to take another look to see if that's still the case, though. WV-571 is the internal reference ticket from before our Github days. |
You could set a short timeout for the cache, say 10 minutes, which would be of some benefit in reducing traffic. The browser will automatically validate the data with the server, getting a 304 response (not modified) if the file has not changed. This requires a server round-trip but doesn't send the data again. For more information see https://devcenter.heroku.com/articles/increasing-application-performance-with-http-cache-headers . The timeout would be 600. |
This is being addressed by GIBS: GIBS-37 |
This is now being addressed by ONEARTH: ONEARTH-513 |
Now being addressed in: GITC-992 |
@mcechini Will this be addressed in GIBS? |
Yes, but not until OnEarth 2.x is servicing request... so still another year away. But I would like to see smarter caching someday |
tile server used by https://worldview.earthdata.nasa.gov has http caching disabled :
setting a http header like cache-control:public, max-age=31536000 for static image data as in the case of map tiles will improve performance dramatically
The text was updated successfully, but these errors were encountered: