[OASIS Issue Tracker] (ODATA-1360) Clarify that clients have to do content-ID replacing to interpret Location headers in batch results

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

Matthew Borges created ODATA-1360:
-------------------------------------

             Summary: Clarify that clients have to do content-ID replacing to interpret Location headers in batch results
                 Key: ODATA-1360
                 URL: https://issues.oasis-open.org/browse/ODATA-1360
             Project: OASIS Open Data Protocol (OData) TC
          Issue Type: Improvement
          Components: Protocol
            Reporter: Matthew Borges


A server is allowed to return a relative to the request URL in the Location header in the response. In a batch request, a request URL can contain a content-ID reference, like $1/Orders to create an order to a not yet created customer. The server can return a Location header of ../Orders(2020) in the response. For the client to be able to determine the correct location of the new Order it MUST perform the content-ID replacement in the request URL (because $1 is not necessarily a single path segment).



We should clarify this by explicitly stating that these steps are required by clients under these circumstances.



--
This message was sent by Atlassian Jira
(v8.3.3#803004)