URL resolution can be done on server-side when a proxy/router is involved

[paraita]

When a third party (proxy/router) is set in front of the catalog service, the latter is not aware of the domain exposed by the third party and is not capable to generate valid URLS anymore. It is partially fixed for HATEOAS by #44 but not for the Swagger UI which still uses the local interface by default.
A possible fix/improvement would be to let that third-party add a special metadata in the header so the catalog service is aware of the forwarding, as explained in this link.
This should also be explained somewhere in the documentation.