URI of created resource

[namedgraph]

In the example Creating documents (files), what is the URI of the created resource? Location response header is missing.

[csarven]

I suppose (and propose) that this should make it into solid-spec:

• Ultimately it is implementation specific ( https://tools.ietf.org/html/rfc7231#section-7.1.2 ) ie. the server allocates the URI.
• Some implementations MAY process Slug in the header request ( https://www.w3.org/TR/ldp/#h-ldpc-post-slug ) ie. the server may ignore it, use it as is, or incorporate it into own pattern.

[RubenVerborgh]

You’re looking for Content-Location.

[namedgraph]

Not according to LDP 5.2.3 HTTP POST

[RubenVerborgh]

I found:

For a 201 (Created) response to a state-changing method, a Content-Location field-value that is identical to the Location field-value indicates that this payload is a current representation of the newly created resource.

—https://tools.ietf.org/html/rfc7231#section-3.1.4.2

But I stand corrected:

The Content-Location header field (Section 3.1.4.2) differs from Location in that the Content-Location refers to the most specific resource corresponding to the enclosed representation. It is therefore possible for a response to contain both the Location and Content-Location header fields.

—https://tools.ietf.org/html/rfc7231#section-7.1.2