-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
No matches returns a 400 - Bad request error #70
Comments
204 No Content would be perfect. |
As mentioned by @jimcue the JSON API spec states that the response code in this scenario MUST be |
d-m-
added a commit
to d-m-/jsonapi
that referenced
this issue
Apr 12, 2018
xiaohutai
added a commit
that referenced
this issue
Apr 23, 2018
Return empty lists with status 200 instead of 400 - Fix for issue #70
Fixed via #80. |
Should be fixed in v3.2.0 |
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
A well-formed request that returns no results will get a 400 HTTP code (Bad request) error response.
With no item with id>100 the request
http://example.com/json/articles?filter[id]=>100
gets:Would it not make sense to get a 200 HTTP response with an empty list (or null for specific-item requests) as mentioned in the JSON API specs?
The text was updated successfully, but these errors were encountered: