Change Details

After the investigation done in {T295050} we think it's beneficial to enforce some caching (e.g. 1 day) when a `mapdata` query API request is made with an old revision id. Requests with the latest revision should not be touched.

After the investigation done in {T295050} we think it's beneficial to enforce some caching. There are 3 situations: 1. Cache for 1 day when a `mapdata` query API request is made with an old revision id. 2. Requests with the latest revision can also be cached because the group ids are unique hashes that never change. Something like 5 minutes sounds like a good starting point. 3. In case of an error no caching should happen, as the error might be resolved the next second.

After the investigation done in {T295050} we think it's beneficial to enforce some caching (e.g. There are 3 situations: 1. Cache for 1 day when a `mapdata` query API request is made with an old revision id. 2. Requests with the latest revision can also be cached because the group ids are unique hashes that never change. Something like 5 minutes sounds like a good starting point. 3. 1 day) when a `mapdata` query API request is made with an old revision id.In case of an error no caching should happen, Requests with the latest revision should not be touchedas the error might be resolved the next second.