When calling the ADES Rest-api, e.g. /{WORKSPACE_NAME}/wps3/processes, the WORKSPACE_NAME does not support all characters but only a limited subset. So e.g. the URL /test-user/wps3/processes causes a 404-Not-Found while the URL /test_user/wps3/processes works as expected. This seems to be related to the '-' character. Also e.g. '=' causes similar issues.
Is there somewhere a documented list of supported characters?
Especially the character '-' is problematic, as UUIDs are based on this and many systems use UUIDs as user ID. So e.g. COIH provides such IDs and ADES not supporting such IDs as workspace name is very inconvenient.
Observed with ADES V1.2.0
When calling the ADES Rest-api, e.g. /{WORKSPACE_NAME}/wps3/processes, the WORKSPACE_NAME does not support all characters but only a limited subset. So e.g. the URL
/test-user/wps3/processescauses a 404-Not-Found while the URL/test_user/wps3/processesworks as expected. This seems to be related to the '-' character. Also e.g. '=' causes similar issues.Is there somewhere a documented list of supported characters?
Especially the character '-' is problematic, as UUIDs are based on this and many systems use UUIDs as user ID. So e.g. COIH provides such IDs and ADES not supporting such IDs as workspace name is very inconvenient.
Observed with ADES V1.2.0