The 422's I believe are hardcoded into the dingo exceptions for store, update, and delete. But I could be mistaken.    

---Hunter Skrasekhunterskrasek@me.com

On May 23, 2014 at 5:16:30 PM CDT, Phil Sturgeon <notifications@github.com> wrote:In src/Routing/Router.php:  > $response = Response::makeFromExisting($response)->morph($this->requestedFormat); > } > > + // Force the response to always return "200 OK" > + // Chances are if the client is requesting jsonp their browser > + // wont implement 422 etc and will drop the body > + if ($this->requestedFormat == 'jsonp') { > + if (!in_array($response->getStatusCode(), [404, 200])) { > + $response->setStatusCode(200); > + } > + } > +   422 is a client error. 200 means everything is fine.   This is terrible. I have a whole slide about the problems this causes in my talk.  Please don't do this.   422 is often used for validation, but it is reserved for WebDAV and not officially in the HTTP spec. Just tell whoever is using PhoneGap and 422's to switch to 400 and you'll be fine.  —Reply to this email directly or view it on GitHub.