configuration parameter @web.application_root_url@ neglected in content view

[jane-heller-bkg]

When viewing register items through the content view, the link presented in the column Status for each item is constructed falsely. It should probably follow @web.application_root_url@. Currently it is built using the local listen interface of the tomcat instance (e.g. http://127.0.0.1:8080//status/valid) and contains a duplicate slash.

[jane-heller-bkg]

This is also related to #367
URL generation should probably be overhauled in generally, because it seems faulty at different places.

[iratigarzon]

Dear @jane-heller-bkg,

The URL for the status column is based on the baseuri attribute of the reg_statusgroup table. If you encounter a duplicate slash in the URL, it may be because the baseuri attribute in reg_statusgroup is empty. Here is an example from our local instance to help you make a modification in the mentioned table.

In our case, we have the following information in the reg_statusgroup table:

When we click on the status column, it redirects us to http://host.docker.internal/registry/status/valid, showing the following information:

I hope this information helps you resolve the issue.

Best regards,

Irati.

[arantzaetxebarria]

Dear @jane-heller-bkg

Did you find the above explanation provided useful?
Do you happen to have any news on this?

Best regards

[jane-heller-bkg]

Hello @arantzaetxebarria

no, unfortunately updating the mentioned field in the database did not change the URL in frontend. (I issued: UPDATE reg_statusgroup SET baseuri = '{CORRECTURI}';

Also having multiple random places like different configuration variables, static variables in the code and database fields that are not documented and all should point to the same URL is in no way feasible. See also the other tickets: #367 and #438

Please update the software so that it generates URLs in a congruent manner, eg. fed from a single configuration variable.

Best

Jane