According to the http spec[1], it says status codes are extensible[2] unless it preserve it class (for ex: 4xx for client errors). I think we can define our own status code and add it in our documentation. For ex cloudflare(reverse proxy) sent 520 when it receives invalid response from origin server. WDYT?
[1] - https://tools.ietf.org/html/rfc2616 [2] - HTTP status codes are extensible. HTTP applications are not required to understand the meaning of all registered status codes, though such understanding is obviously desirable. However, applications MUST understand the class of any status code, as indicated by the first digit, and treat any unrecognized response as being equivalent to the x00 status code of that class, with the exception that an unrecognized response MUST NOT be cached On Thu, Jan 17, 2019 at 8:35 AM Sanjeewa Malalgoda <sanje...@wso2.com> wrote: > I do not think 422 is correct for issues with response. Usually 4XX errors > used to indicate client/request errors. In this case its error or issue > with backend. And for client it can consider as internal server error as > well. Or we can indicate content related issue. 5XX response would be > better. But to be honest i do not have other good suggestion :( > > Thanks, > sanjeewa. > > On Wed, Jan 9, 2019 at 8:21 PM Harsha Kumara <hars...@wso2.com> wrote: > >> +1 we should use 422. >> >> [1] >> https://www.quora.com/Which-HTTP-code-is-best-suited-for-validation-errors-400-or-422 >> [2] >> https://stackoverflow.com/questions/1959947/whats-an-appropriate-http-status-code-to-return-by-a-rest-api-service-for-a-val >> >> On Wed, Jan 9, 2019 at 3:22 PM Uvindra Dias Jayasinha <uvin...@wso2.com> >> wrote: >> >>> 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 >>> >> >> >> -- >> >> *Harsha Kumara* >> >> Associate Technical Lead, WSO2 Inc. >> Mobile: +94775505618 >> Email: hars...@wso2.coim >> Blog: harshcreationz.blogspot.com >> >> GET INTEGRATION AGILE >> Integration Agility for Digitally Driven Business >> > > > -- > *Sanjeewa Malalgoda* > Software Architect | Associate Director, Engineering - WSO2 Inc. > (m) +94 712933253 | (e) sanje...@wso2.com | (b) Blogger > <http://sanjeewamalalgoda.blogspot.com>, Medium > <https://medium.com/@sanjeewa190> > > GET INTEGRATION AGILE <https://wso2.com/signature> > Integration Agility for Digitally Driven Business > _______________________________________________ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > -- *Rajith Roshan* | Senior Software Engineer | WSO2 Inc. (m) +94-717-064-214 | (e) raji...@wso2.com <shen...@wso2.com> <https://wso2.com/signature>
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
