NCNv1: Bad requests always return 422 rather than 400 #141

Closed
opened 5 years ago by jking · 0 comments
jking commented 5 years ago
Owner

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.

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.
jking added this to the 0.5.0 milestone 5 years ago
jking added the
documentation
label 5 years ago
jking changed title from NCNv1: Bad requests should always return 422 rather than 400 to NCNv1: Bad requests always return 422 rather than 400 5 years ago
jking closed this issue 5 years ago
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.