Why does the FDP (API) need to be aware of a clientUrl?

[dennisvang]

From my naive point of view, I would expect an FDP (API) to be completely unaware of any clients.

However, the configuration of the FDP requires a clientUrl to be specified. Also see this search.

This seems to me like an undesirable coupling.

• Why does the FDP need to be aware of a clientUrl?
• Should this coupling be removed?

[dennisvang]

Does this have something to do with the inconvenient fact that our "reference" FDP-client Docker image includes a reverse-proxy for the FDP, as discussed in FAIRDataTeam/FAIRDataPoint-client#157?

In that case, is it just a matter of unfortunate choice of variable name? Should the setting be called e.g. apiUrl or publicUrl, instead of clientUrl?

Also note that there is a persistentUrl setting as well.