Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
If you are looking for /Resource/Id and that resource does not exist, I had always though that 404 was the appropriate response. However, when returning null from a Jersey handler, I get back a “204 No Content”. I can likely work with either one, but am curious to others thoughts on this.
To answer my own next question. To get Jersey to return 404 you must throw an exception.
if (a == null)
throw new WebApplicationException(404);
The HTTP Code Definition states that the codes beginning with 2 are for successful calls and 4 for unsuccessful ones.
When you get the 204 it just shows you that there is nothing to return (usually you expect if you make a POST or PUT call that does not need to return anything)
When you get a 404 it states that the call was unsuccessful, so it will not return anything.
In your situation the 404 is appropriate, not the 204! Since you probably want to say to the caller that he made a wrong call.