Problems with file paths in URL paths (user files)

[m-mohr]

Having the file path of the user files in the URL path seems to be a problem for some software packages, e.g. plumber and browsers. We might need to put the file paths into the query.
See Open-EO/openeo-r-backend#7 for more information.

Remark: RFC 3986 says in 2.3 that dots in URLs should not be encoded. Therefore we should not have specified in the API that dots need to be URL encoded as proposed in the linked issue.

[m-mohr]

I think we shouldn't have workarounds for back-end limitations in the API. Therefore we stick with the current behavior for now.

[m-mohr]

Must admin that restify for NodeJS has also problems with slashes in path parameters. What about the other back-ends? We might reconsider putting the path into the query of a URL, but that's not "REST".

[m-mohr]

We must specify that all path parameters (user_id, job_id, service_id, process_graph_id) except data_id/product_id and path must not contain slashes.

[m-mohr]

Could be solved with #135 - wait for a decision on that issue.

[m-mohr]

It's an OpenAPI and/or tooling limitation after all, closing until further feedback has arrived.