In our beta environments, when downloading a collection artifact from /api/v3/plugin/ansible/content/published/collections/artifacts/<file>.tar.gz there is an infinite loop that prevents downloads:

• /api/v3/artifacts/collections/published/ <file>.tar.gz
• /api/content/published/v3/plugin/ansible/content/published/collections/artifacts/ <file>.tar.gz
• /api/v3/artifacts/collections/published/ <file>.tar.gz
• /api/content/published/v3/plugin/ansible/content/published/collections/artifacts/ <file>.tar.gz (etc)

In our beta-galaxy environments, we worked around this via proxying the download url to the content-app

location ~ /api/v3/artifacts/collections/(.+)/ {
    proxy_pass http://content-app;
} 

But that is not a workaround needed in other installations. Note in other installations `/api/<automation-hub|galaxy>/` but beta environments use shorter paths

PULP_GALAXY_API_PATH_PREFIX = /api/
PULP_CONTENT_PATH_PREFIX = /api/v3/artifacts/collections/ 

This issue was noticed when we changed upload urls from `/api/content/inbound-<namespace>/v3/artifacts/collections/` to `/api/v3/artifacts/collections/` … and this conflicted with our content-app proxy. But we adjusted our workaround content-app proxy to only activate when there is more path after `/collections/` as this implies a download.

The workaround may be sufficient, but we should look into the cause of this.