Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[OpenAPI] unindex/remove operations accept URIs via form data and not just query #512

Open
Enet4 opened this issue Sep 29, 2021 · 0 comments

Comments

@Enet4
Copy link
Collaborator

Enet4 commented Sep 29, 2021

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant