This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
Accept
Reject
Preferences
Log in to ask a question
Log in to ask a question

Handling no resource created in POST

Posted on 03-01-2016 07:27 PM
Not applicable
Reply posted on --/--/---- --:-- AM

In case of a search functionality, is it "fair" to use POST because search results are being created dynamically? If so, what HTTP error code be suitable in case search does not generate any results? Can "204" be used?

0 2 449
Topic Labels
0 Likes
2 REPLIES 2

Posted on --/--/---- --:-- AM
Abhishek_Subram
New Member
Reply posted on --/--/---- --:-- AM

A search should be a GET. I think we can have a payload with GET with the search criteria. 204 No Content is applicable for GET, PUT & DELETE, hence you can send it if you use GET.

0 Likes

Posted on --/--/---- --:-- AM
anilsr
Staff
Reply posted on --/--/---- --:-- AM

@Shailesh Bhaskaran ,

Adding on top of @Abhishek Subramanya , You are going to fetch search results (information) which already existed somewhere. I believe GET is more appropriate then POST.

For example, Google Custom Search API uses GET method & response with Status code 200 OK.

Short Answer, It should be GET & 200