Before this PR the context path was used as start of the relative serverUrl, followed by "dataset/{datasetId}". If an Apache Webserver or NGINX is used and the configuration does not include the context path the serverUrl was wrong.
Example:
Requesting the OpenAPI document with https://ogc-api.server.de/datasets/test/api the OpenAPI document contains the serverUrl 'deegree-ogcapi/datasets/test/api'. The execution of requests with the Swagger UI results in invalid URLs: https://ogc-api.server.de/deegree-ogcapi/datasets/test/collections
This PR fixes the serverUrl in the OpenAPI document. Instead of the relative url an absolute url is used. Using the example above the serverUrl results in https://ogc-api.server.de/datasets/test/ and execution of request with the Swagger UI is possible.
Before this PR the context path was used as start of the relative serverUrl, followed by "dataset/{datasetId}". If an Apache Webserver or NGINX is used and the configuration does not include the context path the serverUrl was wrong. Example: Requesting the OpenAPI document with https://ogc-api.server.de/datasets/test/api the OpenAPI document contains the serverUrl 'deegree-ogcapi/datasets/test/api'. The execution of requests with the Swagger UI results in invalid URLs: https://ogc-api.server.de/deegree-ogcapi/datasets/test/collections
This PR fixes the serverUrl in the OpenAPI document. Instead of the relative url an absolute url is used. Using the example above the serverUrl results in https://ogc-api.server.de/datasets/test/ and execution of request with the Swagger UI is possible.