Download Location should use "/full" when downloading relations

[skyper]

What steps will reproduce the problem?

1. Have an ​URL of a relation in buffer and an active data layer
2. Paste or use Download Location to download the relation

What is the expected result?

The relation is downloaded with /full and it is fast

What happens instead?

A lot of download traffic and history queries, like each member object and its children are downloaded on their own. I canceled the download as it took too long.

Please provide any additional information below. Attach a screenshot if possible.

Now, do the same with Download Object and see how fast it is and how much less it stresses the server.

See also #21904

Relative:URL: ^/trunk
Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
Last:Changed Date: 2022-02-18 08:34:05 +0100 (Fri, 18 Feb 2022)
Revision:18382
Build-Date:2022-02-19 02:31:08
URL:https://josm.openstreetmap.de/svn/trunk

Identification: JOSM/1.5 (18382 en) Linux Debian GNU/Linux 11 (bullseye)
Java version: 17.0.2+8-Debian-1deb11u1, Debian, OpenJDK 64-Bit Server VM

[skyper]

Actually, I do not understand why the full relation is downloaded and not just the relation with incomplete members. Anyway either use /full or do not download members.

[GerdP]

I tried with your link ​https://www.openstreetmap.org/relation/13881382 and I see

2022-03-13 17:13:42.820 INFO: GET https://api.openstreetmap.org/api/0.6/relations?relations=13881382 -> HTTP/1.1 200 (198 ms)
2022-03-13 17:13:43.258 INFO: GET https://api.openstreetmap.org/api/0.6/relation/13881382/full -> HTTP/1.1 200 (405 ms)
2022-03-13 17:13:43.607 INFO: GET https://api.openstreetmap.org/api/0.6/relation/13881382/relations -> HTTP/1.1 200 (131 ms)

So, it use /full and doesn't download any history. Maybe a preference difference?

[skyper]

Strange, I cannot reproduce it either. Not with my common preferences nor without preferences. Sorry for the noise.​