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

Closed
opened 2018-11-07 10:48:48 -05:00 by jking · 0 comments
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 2018-11-07 10:48:48 -05:00
jking changed title from NCNv1: Bad requests should always return 422 rather than 400 to NCNv1: Bad requests always return 422 rather than 400 2018-11-07 10:49:02 -05:00
jking closed this issue 2018-11-07 13:02:15 -05:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: MensBeam/Arsse#141
No description provided.