[openstreetmap/openstreetmap-website] Make the Multi fetch response more friendly for hidden versions of objects (Issue #5005)

[Roman Deev]

### Problem

[Multi Fetch](https://wiki.openstreetmap.org/wiki/API_v0.6#Multi_fetch:_GET_/api/0.6/[nodes|ways|relations]?#parameters) requests return HTTP 404 without a hint about which argument caused the error

### Description

For example, y https://www.openstreetmap.org/node/250407804/history the first versions are hidden.

If you do https://www.openstreetmap.org/api/0.6/nodes.json?nodes=250407804v1 you will receive an HTTP 404. But what if you request a hundred nodes and there are several hidden versions among them? https://www.openstreetmap.org/api/0.6/nodes.json?nodes=250407804,250407804v1

You'll get a 404, but you won't be able to figure out which version caused the error. And to understand this, you will have either split the query, or call /history for each object, which kills the idea of Multi Fetch queries.

## Possible solutions

1. Return visible versions, but no hidden versions (just like for deleted nodes)
2. Return a 404 and a list of problem nodes

p. s. the same applies for ways and relations

### Screenshots

_No response_

-- 
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/issues/5005
You are receiving this because you are subscribed to this thread.

Message ID: <openstreetmap/openstreetmap-website/issues/5005 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/rails-dev/attachments/20240719/0945e770/attachment.htm>