OPS returning stale results
Posted: Sun Jan 14, 2018 9:23 am
Dear OPS support,
I have now observed the following: Sometimes the OPS servers simply return the result from the previous query, instead of returning the results of the subsequent query. This is then visible from the ETag response header, which is identical between subsequent responses. It is then also visible from the content-length response headers which also remain constant between subsequent responses. In such situtations, the user is thus provided with stale data from his previous request, instead of data corresponding to his new request. This may happen even when all throttles are "green", you are not anywhere of exhausting one of your quotas, and the servers are in state "idle". Is this correct, and if so, what is the purpose of this behaviour?
mike_k43
I have now observed the following: Sometimes the OPS servers simply return the result from the previous query, instead of returning the results of the subsequent query. This is then visible from the ETag response header, which is identical between subsequent responses. It is then also visible from the content-length response headers which also remain constant between subsequent responses. In such situtations, the user is thus provided with stale data from his previous request, instead of data corresponding to his new request. This may happen even when all throttles are "green", you are not anywhere of exhausting one of your quotas, and the servers are in state "idle". Is this correct, and if so, what is the purpose of this behaviour?
mike_k43