While examining at access logs on logstash I saw that quite a lot of requests related to thresholds that are not made by the ores extension (made by user_agent python-requests)

select Time, level, host, user_agent, uri, return_code, response_size, method, duration from logstash-default-1-7.0.0-1-2023.07.08
where host like '%ores%'
and uri like '%thresholds%'
limit 100;

This should be further investigated and if required we should do the following:

• • Check if the requested thresholds are the default (hardcoded ones) that we use in ores extension. If so we can just do a similar thing like we do in the extension and serve them from a file.
• If the thresholds are different and we want to support this then we will need to work on the revscoring model server to allow querying the model directly when extra payload is included in the post body of the request. Then we could handle these requests in ores-legacy by translating them in the corresponding LW requests.