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

Explicitly state server behaviour when a client uses $select/$expand for an update response

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: V4.01_CS02
    • Component/s: Protocol
    • Labels:
      None
    • Environment:

      Applied

    • Proposal:
      Hide

      Clarify that if the client specifies a $select and/or $expand for the response of a PATCH/PUT request, that the server MUST respond with a a response body. If the service uses ETags for optimistic concurrency, the entities in the response MUST include ETags.

      Show
      Clarify that if the client specifies a $select and/or $expand for the response of a PATCH/PUT request, that the server MUST respond with a a response body. If the service uses ETags for optimistic concurrency, the entities in the response MUST include ETags.
    • Resolution:
      Hide

      https://www.oasis-open.org/committees/download.php/65911/odata-v4.01-wd07-part1-protocol-2019-09-18.docx

      Show
      https://www.oasis-open.org/committees/download.php/65911/odata-v4.01-wd07-part1-protocol-2019-09-18.docx

      Description

      Clients need a guaranteed way to get certain information in the response to PATCH/PUT such as an updated ETag.  Clarify that if the client specifies a $select and/or $expand for the response of a PATCH/PUT request, that the server MUST respond with a a response body including the ETag.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              matt.borges Matthew Borges
            • Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: