I would not return a Location header, but I guess that should depend on the implementation.  For instance, a server may want the client to use the returned Location to check to see when the resource is actually created.  E.g . "I've accepted the post, if and when I create it, it will be available here...."

On 3/15/06, Michael Bernstein < [EMAIL PROTECTED]> wrote:

On Wed, 2006-03-15 at 01:04 -0800, James Snell wrote:
> The HTTP response that is returned back to the POSTing client is
> required only to reflect the specific context of that individual
> specific transaction.  That is, even if the POSTing results in the
> creation of some kind of resource, if that resource is not being made
> available to that POSTing client to do anything with, or if the
> resource is being automatically added to some moderation queue, it is
> appropriate to return a 202 Accepted.

OK, I learned something.

Do you still maintain that the server should not send a location header
(if only for the client's future reference)? It still seems to me that
this needlessly hides useful information.

- Michael




--
- James Snell
  http://www.snellspace.com
   [EMAIL PROTECTED]

Reply via email to