NCNv1: Bad requests always return 422 rather than 400 #141
Labels
No labels
admin tools
api
bug
documentation
duplicate
enhancement
feature
help wanted
in progress
internals
invalid
packaging
question
testing
trivial
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: MensBeam/Arsse#141
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
NextCloud News incorrectly return 422 even with syntactically invalid input in contravention of RFC 4918; The Arsse does not, returning 400. Rather than mimic this bug, the difference should be documented.
Moreover, if syntactically invalid JSON is provided, NCNv1 will ignore it and use GET parameters instead. We will not do this.
NCNv1: Bad requests should always return 422 rather than 400to NCNv1: Bad requests always return 422 rather than 400