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
changed title from NCNv1: Bad requests should always return 422 rather than 400 to NCNv1: Bad requests always return 422 rather than 4005 years ago
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 5 years ago