I think 422 is the most appropriate given your use case of validating if a message matches a given schema. So you can receive a valid JSON or XML(it's not malformed hence it is not a bad request(400)), but it may not match with the message schema definition you are matching against.
The specs dont seem to talk about processing from the perspective of the response. I guess you can use the same code used for the request. On Wed, 9 Jan 2019 at 14:54, Shalki Wenushika <wenush...@wso2.com> wrote: > Hi all, > > This is related to the mail thread subjected as “[Architecture]API schema > based request/response validator for Microgateway”. I’m validating > requests/responses coming to the microgateway and send error messages to > the client if the request/response is invalid. > > When a client sends a request to the microgateway if the request is > invalid I’m sending an error message with the HTTP status code > 422(Unprocessable entity) to the client. And also I’m doing the response > validation. If the response coming from the backend is invalid I send an > error message to the client. I need to know what will be the most > appropriate HTTP status code to be included in the error if the response is > invalid. > > Thank you! > > -- > > *Shalki Wenushika* > *Software Engineering Intern* > WSO2 (University of Moratuwa) > *mobile *: *+94 716792399* | *email *: > <http://c.content.wso2.com/signatures/wso2-signature-general.png> > wenush...@wso2.com > > > > -- Regards, Uvindra Mobile: 777733962
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
