W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2011

Re: Indicating a resource does not exist

From: Nathan <nathan@webr3.org>
Date: Thu, 20 Jan 2011 14:47:27 +0000
Message-ID: <4D384AFF.3090807@webr3.org>
To: Joe Gregorio <joe@bitworking.org>
CC: HTTP Working Group <ietf-http-wg@w3.org>
Joe Gregorio wrote:
> On Thu, Jan 20, 2011 at 9:31 AM, Nathan <nathan@webr3.org> wrote:
>> Joe Gregorio wrote:
>>> What's wrong with 404 Not Found?
>>   404 Not Found
>>   ...
>>   The server has not found anything matching the effective request URI.
>>   No indication is given of whether the condition is temporary or
>>   permanent ...
>> The best you can conclude from that is "don't know" the state of the
>> resource, or if there is one.
> OK, so 410 Gone if you want to indicate it is permanent.

410 entails more though, "was a resource, is no longer a resource", 404 
is "I don't know", I'm looking for an unambiguous "origin server says 
this is not a resource"

Essentially at the minute, the only resource states that can be conveyed 
(as far as I can see) are:

  - created (POST/PUT 201, PUT 204)
  - current state (many combinations)
  - state changed (POST/PUT 200)
  - unknown state (DELETE 202, a few 3xx, most 4xx and all 5xx)
  - gone (204)

so basically, there's no way to say "no resource".


Received on Thursday, 20 January 2011 14:49:32 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 11:10:56 UTC