fix(submission): handle missing xml file with digest authentication DEV-1038 #6428
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🗒️ Checklist
#Support Docs Updates, if any<type>(<scope>)<!>: <title> DEV-1234Front endand/orBack endorworkflow📣 Summary
Prevent server errors when clients using Digest authentication send empty submission requests to the openrosa
/<username>/submissionendpoint.📖 Description
Previously, when a client (such as curl using --digest) attempted to submit to
https://kobocat/<username>/submissionfor a form that does not allow anonymous submissions, the first unauthenticated request in the Digest handshake was accepted by the view.Because this initial request contained no body and no authentication header, the view attempted to read a
Nonefile instance, leading to:This caused a 500 error before the client’s second (authenticated) request could be processed.
This PR adds a validation to check whether
xml_fileis missing or empty. When this happens, the server now fails fast with a properOpenRosaResponseBadRequest (400)and a clear, informative error message.👀 Preview steps