[atlas] Caching issues on the latest call
- Previous message (by thread): [atlas] half dead v1 probe ?
- Next message (by thread): [atlas] New RIPE Atlas Measurement Options
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Johan ter Beest
jterbeest at ripe.net
Thu Jul 13 17:19:05 CEST 2017
Dear all, Today we became aware of some caching issues on the latest API call (https://atlas.ripe.net/docs/api/v2/reference/#!/measurements/Latest_GET). In certain corner cases it was possible that an incomplete set of results for a logged-in user was cached for up to 24 hours. This did not apply to non logged-in users as the results are not cached in that case. A fix for this issue has been deployed and going forward the latest call will have a 1 minute cache regardless of whether the user is logged in or not. As caching is always tricky, we kindly ask that users will let us know if they experience anything out of the ordinary that might be related to this change. Kind regards, Johan ter Beest RIPE Atlas Team
- Previous message (by thread): [atlas] half dead v1 probe ?
- Next message (by thread): [atlas] New RIPE Atlas Measurement Options
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]