You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Web API specification in dicoogle_web_api.yaml suggests that the operations /management/tasks/unindex and /management/tasks/remove receive all input via the query string. This would be accepted by Dicoogle, but the URIs to unindex or remove are preferably passed as a form data object (url-encoded) so that they do not make the URI too long. This has been the case since Dicoogle 2, so the specification is missing this particular detail.
The operations mentioned above should be documented so that they accept multiple URIs via form data, and that users should prefer this way of passing the uri parameter over passing it via the query string.
The text was updated successfully, but these errors were encountered:
The Web API specification in dicoogle_web_api.yaml suggests that the operations
/management/tasks/unindex
and/management/tasks/remove
receive all input via the query string. This would be accepted by Dicoogle, but the URIs to unindex or remove are preferably passed as a form data object (url-encoded) so that they do not make the URI too long. This has been the case since Dicoogle 2, so the specification is missing this particular detail.The operations mentioned above should be documented so that they accept multiple URIs via form data, and that users should prefer this way of passing the
uri
parameter over passing it via the query string.The text was updated successfully, but these errors were encountered: