Permanent links to release assets: not found (404)
Summary
Not sure it's a duplicate of #211622 (closed).
I am trying the new permanent link feature, but when links are created, if I follow them, I have a 404 response with a message saying “The page could not be found or you don't have permission to view it.”
Steps to reproduce
On my project, I created a release, and used the API to create some links on it providing a filepath. For this, I am using a POST query as explained in the documentation. The real url is targeting an artifact made by a job of the project (internal link).
When viewing the release, the link is there, with the correct name. The target URL looks correct also, even if the “downloads” part, stated by this documentation is not present.
When requesting the links with a GET request, I get all the links with values which seem corrects (but again, the “downloads” part is not present).
But when I click on the link, or when I manually enter the address in the address bar of my browser, I get a 404 page. Note that this is not the simple page not found, but the page not found or permission one. Anyway, there should not be a specific permission to view the permanent links, should there?
On the contrary, if I try to manually add the missing “downloads” part, I have the simple page not found.
Note that if I enter the real url in the address bar of my browser, instead of the direct_asset_url, I can download the asset.
Our GitLab is in version 12.10.2.
Example Project
For the moment, the links are tested in my internal fork: https://git.duniter.org/sveyret/duniter/-/releases#v1.8.4
If the link does not work, this will be because I deleted my fork after my modifications were merged into the main project, which you can find here: https://git.duniter.org/nodes/typescript/duniter
What is the current bug behavior?
“The page could not be found or you don't have permission to view it” (HTML 404) when trying to follow a release asset link.
What is the expected correct behavior?
Should download the asset.