Skip to content

api: Handle origin URLs mangled by HTTP client when querying endpoints

Some HTTP clients (java one for instance) can turn double slashes in URL path into a single one which breaks the use of SWH Web API when querying origin related endpoints.

So ensure to demangle such origin URLs received as endpoint arguments to workaround those issues.

Related to #4769 (closed).

Merge request reports