Re: Section 9.4 POST

Paul Leach <> says:
> Section 9.6 says:
>If a resource has been created on the origin server, the response SHOULD
>be 201 (Created) and contain an entity which describes the status of the
>request and refers to the new resource.
>Should it says that it SHOULD also return a Content-Location: when a
>resource has been created? Or at least refer to the Content-Location
>section to indicate the possible desirability of same?

What interoperable operations would be enabled by such a
recommendation?  My belief is that we need very good reason to
specifying new behavior that was not in 1.0 or previous versions of
1.1, and that if we've not recommended a Content-Location in the past,
we shouldn't recommend one now without some compelling reason.

We've had compelling reasons to fix caching, add host headers, and
finally enable at least some kind of reliable content-negotiation, but
neither range-PUT nor content-location-on-POST fall into this


Received on Friday, 31 May 1996 22:38:45 UTC