W3C home > Mailing lists > Public > www-tag@w3.org > March 2010

Re: 204 No Content for a resource which is known but has no representation yet?

From: Nathan <nathan@webr3.org>
Date: Sun, 14 Mar 2010 01:12:19 +0000
Message-ID: <4B9C37F3.3020802@webr3.org>
To: Reto Bachmann-Gmür <reto@gmuer.ch>
CC: ietf-http-wg@w3.org, www-tag@w3.org
Thanks for getting back to me so quickly Reto,

Reto Bachmann-Gmür wrote:
> Hi Nathan
> 
> Returning 204 would be against the resultion of HttpRange-14 as a 2XX
> response implies the identified resource is an information resource
> and you are not.

Well noted about httprange-14! However this could easily be an
information resource that is "coming soon", for example I am writing a
document that will be available at 'uri' next week.

> So either return a 404, or return a 303 response pointing to a URI
> that currently (as no representation is available) yields to a 404.

303 to a resource which 404's sounds like it could work.. 404 I am keen
to avoid.

Can you use a 3xx without a Location header?

> Cheers,
> Reto
> 
> On Sun, Mar 14, 2010 at 1:38 AM, Nathan <nathan@webr3.org> wrote:
>> Hi All,
>>
>> Can I use a 204 No Content to indicate that a resource is known but
>> currently does not have a representation (or another resource which
>> describes it)?
>>
>> example:
>> I have a resource which is a conceptual map to "me"; I have assigned a
>> URI to that resource, am in the process of creating a document which
>> describes me, and when I am done I will 303 See Other to the document
>> from the resource which is a conceptual map to "me".
>>
>> In the interim what status code can I use to say that the resource is
>> known, does not have a representation of its own that can be transferred
>> by the server over HTTP, another resource is not know that is
>> descriptive of said resource & the resource identifier is not to be used
>> for anything else.
>>
>> I've fully checked through all status codes, including the 4xx's but
>> can't find any to use, and 204 No Content seems to fit the best as far
>> as I can tell.
>>
>> Many Thanks,
>>
>> Nathan
>>
>>
> 
> 
Received on Sunday, 14 March 2010 01:13:02 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 26 April 2012 12:48:20 GMT