> On 15/08/2019, at 20:12, Илья Страхов <ilya.strahov@xxxxxxxxx> wrote: > > Hello. > I want to hear the opinion of the community and offer a separate HTTP > code for the situation when the client has sent data that on the side > of business logic is processed with an error. > > An example in the context of the REST. > 1) If the client did not pass a required key or syntax error, then the > HTTP 400 response. It's okay. > 2) If the client passed the key and value, further data processing led > to an error when the entity cannot be created/modified for reasons at > the application logic level. For this case, I propose to make a new > HTTP code. Can you please expand more on what kind of application logic error? For example if the value is invalid for that key (whether out of range, wrong type, is external reference where reference doesn’t exist) then it seems to me that 400 would still be suitable. So if you could elaborate on what sort of different failure you are handling when processing the data and how this would be clearly defined for another 4XX code to be usefully handled by processing consumers this may assist others in looking at supporting this suggestion. > Regards Alexander Alexander Neilson Neilson Productions Limited 021 329 681 alexander@xxxxxxxxxxxxxx
