Clarify semantics

[philippeluickx]

To me it is not clear what a frontend and backend prefix is. This is being used in the info display for an API, e.g. https://apika.digipalvelutehdas.fi/api/A844qMfhmoAFGAJMu

I googled the terms and only get meaningful results on our own project.

[bajiat]

@brylie Doesn't your PR #1457 already handle this? Or are there other instances of frontend and backend prefixes outside the Proxy tab in Profile view.

[brylie]

@bajiat it is definately related. @Nazarah and I decided to change frontend and backend for clarity:

• frontend -> Proxy
• backend -> API

We also changed the word 'prefix' to 'base path', to match the Open API Specification.

The base path on which the API is served, which is relative to the host.

The changes can be seen, as you mentioned, in the Proxy Settings UI made available in PR #1457:

[bajiat]

So should we close the issue once PR is merged?

[brylie]

I can associate this issue with the PR, if you agree that it is closed when the PR is merged. There may be a related documentation task, where we create a diagram to clarify these concepts. E.g.

[bajiat]

Documentation could be a non-urgent continuation task.

[brylie]

OK, I have added a 'closes' reference to this task in the PR.