• Type: Bug
    • Resolution: Fixed
    • Priority: Minor
    • None
    • Affects Version/s: V4.0_WD01
    • Component/s: Protocol
    • None
    • Environment:

      [Proposed]

    • Hide

      1. In section 8.4.1, "The Prefer Header", replace:

      "The client MAY specify a Prefer header on Data Modification Request or Action Request."

      with:

      "The client MAY specify a Prefer header value of "return-content" or "return-no-content" on POST, PUT, or PATCH Data Modification Request other than to a named stream property, or to an Action Request. Specifying a value of "return-content" or "return-no-content" in a GET or DELETE request, or any request to a named stream property, SHOULD return a 4xx Client Error.

      A Prefer header value of "return-content" or "return-no-content" MAY be specified on an individual Data Modification or Action request within a batch, subject to the same restrictions, but SHOULD return a 4xx Client Error if specified on the batch request itself."

      2. Add the following to the end of section 10.3.6.2, "Editing a Media Entity Stream":
      "If the request to edit a Media Entity Stream returns a non-empty response body, the response body MUST contain the updated Media Entity."

      Show
      1. In section 8.4.1, "The Prefer Header", replace: "The client MAY specify a Prefer header on Data Modification Request or Action Request." with: "The client MAY specify a Prefer header value of "return-content" or "return-no-content" on POST, PUT, or PATCH Data Modification Request other than to a named stream property, or to an Action Request. Specifying a value of "return-content" or "return-no-content" in a GET or DELETE request, or any request to a named stream property, SHOULD return a 4xx Client Error. A Prefer header value of "return-content" or "return-no-content" MAY be specified on an individual Data Modification or Action request within a batch, subject to the same restrictions, but SHOULD return a 4xx Client Error if specified on the batch request itself." 2. Add the following to the end of section 10.3.6.2, "Editing a Media Entity Stream": "If the request to edit a Media Entity Stream returns a non-empty response body, the response body MUST contain the updated Media Entity."
    • Show
      Applied proposed resolution in https://www.oasis-open.org/apps/org/workgroup/odata/download.php/46906/odata-v1.0-wd01-2012-9-12.doc . Accepted: https://www.oasis-open.org/committees/download.php/46960/odata_meeting-8_on-20120920_minutes.html

      The Prefer header can be used with custom values in addition to "return-content" and "return-no-content". The OData Protocol Version 1.0 spec should specify valid cases for use of those defined values.
      a. Not supported for DELETE.
      b. Not supported for $batch (but supported for requests within a $batch)
      c. Not supported for named streams
      d. Clarify what UPDATE to Media resource stream with "return-content" should return; the binary data or the media link entry? Returning the MLE matches common use cases (replacing the picture might update MLE properties like size, resolution, location, etc.)

            Assignee:
            Michael Pizzo
            Reporter:
            Michael Pizzo
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: