Uploaded image for project: 'OASIS Open Data Protocol (OData) TC'
  1. OASIS Open Data Protocol (OData) TC
  2. ODATA-1360

Clarify that clients have to do content-ID replacing to interpret Location headers in batch results

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: V4.01_OS
    • Fix Version/s: V4.01_ERRATA01
    • Component/s: JSON Format, Protocol
    • Labels:
      None
    • Proposal:
      Hide

      Add a sentence to JSON Format, section 19.2 (and the corresponding section on Multipart Batch in Protocol):

      If the Location header in the response contains a relative URL, clients MUST be able to resolve it relative to the request's URL even if that contains such a reference.

      Show
      Add a sentence to JSON Format, section 19.2 (and the corresponding section on Multipart Batch in Protocol): If the Location header in the response contains a relative URL, clients MUST be able to resolve it relative to the request's URL even if that contains such a reference.
    • Resolution:
      Hide

      https://github.com/oasis-tcs/odata-specs/pull/88

      Show
      https://github.com/oasis-tcs/odata-specs/pull/88

      Description

      A server is allowed to return a URI in the Location header that is relative to the request URL.  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.

        Attachments

          Activity

            People

            • Assignee:
              heiko.theissen Heiko Theissen
              Reporter:
              matt.borges Matthew Borges
            • Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: