RE: Disambiguation; keeping the "U" in "URI"

I think you're confusing "Location" (RFC 2616 section 14.30) with
"Content-Location".

      Note: The Content-Location header field (section 14.14) differs
      from Location in that the Content-Location identifies the original
      location of the entity enclosed in the request. It is therefore
      possible for a response to contain header fields for both Location
      and Content-Location. Also see section 13.10 for cache
      requirements of some methods.

Neither do service for bridging the difference between me and
my web page, but one could imagine using Content-Location as
a reusable URI for the result of POST (although such use is
not defined).

Larry
-- 
http://larry.masinter.net