-
Notifications
You must be signed in to change notification settings - Fork 486
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
Malformed OAI-PMH requests generate an internal server error #9275
Comments
Sure, we will fix this. |
I am pretty sure this is not an error within the XOAI library - there is a test case for this. |
2023/12/19: Prioritized during meeting on 2023/12/18. Added to Needs Sizing. |
Slightly surprised it's still there... |
dataProvider.handle(params) allows us to return the correct error.
@claudiodsf fixed in this PR: Thanks for reporting this! |
dataProvider.handle(params) allows us to return the correct error.
What steps does it take to reproduce the issue?
Try a malformed request, like, e.g., without any keyword:
https://demo.dataverse.org/oai
Or with a bad keyword:
https://demo.dataverse.org/oai?key=value
Always
OAI-PMH protocol
The bad request generates an "Internal Server Error"
All users
The client should get an XML response with an error message from the OAI-PMH protocol.
This used to work on old version of Dataverse, example:
https://entrepot.recherche.data.gouv.fr/oai
https://entrepot.recherche.data.gouv.fr/oai?key=value
(The installation in the example runs Dataverse 5.3)
Which version of Dataverse are you using?
5.12, 5.12.1
Any related open or closed issues to this bug report?
Screenshots:
The text was updated successfully, but these errors were encountered: