Michael Bernstein 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.
In a similar situation (for an internal system) we're returning 202
Accepted, and a Location: header with the URI where the resource will
be located. (In fact a placeholder is put there immediately and is
later replaced with the real resource, but that's a detail.)
|
