We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
If any query string args are invalid, for example invalid JSON in path, we need to catch these errors and send back HTTP 400.
The text was updated successfully, but these errors were encountered:
You must mean 500 correct?
Doh! of course, 400.
Sorry, something went wrong.
400 Bad Request seems appropriate for an invalid JSON path.
On Jun 15, 2015, at 3:11 PM, Michael Paulson notifications@github.com wrote: You must mean 500 correct? — Reply to this email directly or view it on GitHub #16 (comment).
On Jun 15, 2015, at 3:11 PM, Michael Paulson notifications@github.com wrote:
— Reply to this email directly or view it on GitHub #16 (comment).
Yeah it was intentional.
JH
On Jun 15, 2015, at 3:19 PM, mac-a1 notifications@github.com wrote: 400 Bad Request seems appropriate for an invalid JSON path. On Jun 15, 2015, at 3:11 PM, Michael Paulson notifications@github.com wrote: You must mean 500 correct? — Reply to this email directly or view it on GitHub #16 (comment). — Reply to this email directly or view it on GitHub.
On Jun 15, 2015, at 3:19 PM, mac-a1 notifications@github.com wrote:
— Reply to this email directly or view it on GitHub.
ThePrimeagen
No branches or pull requests
If any query string args are invalid, for example invalid JSON in path, we need to catch these errors and send back HTTP 400.
The text was updated successfully, but these errors were encountered: