Status response message as carrier for annotations as alternative to 204 No Content

XMLWordPrintable

    • Type: Improvement
    • Resolution: Won't Fix
    • Priority: Major
    • V4.01_WD01
    • Affects Version/s: V4.0_COS
    • Component/s: Protocol
    • None
    • Environment:

      [Proposed]

    • Hide

      Define a "status" response as a carrier for explanations that can be used with status 200 OK in all situtations that currently require 204 No Content.

      Options:
      1. Define a minimal structure similar to the error response to contain a machine-readable code and a human-readable message
      2. Define just a new context URL (e.g. #odata.status or #Edm.Status) without required structure

      Show
      Define a "status" response as a carrier for explanations that can be used with status 200 OK in all situtations that currently require 204 No Content. Options: 1. Define a minimal structure similar to the error response to contain a machine-readable code and a human-readable message 2. Define just a new context URL (e.g. #odata.status or #Edm.Status) without required structure

      There are some situations where OData 4.0 requires a response with 204 No Content:
      1. GET a raw primitive value using the /$value path suffix and the value is null
      2. GET a nullable property or navigation property and the value is null
      3. DELETE a nullable property or relationship to set it to null
      4. GET a function result that is primitive or structured and is null
      5. POST an action call and the primitive or structured result is null, or the action has no result

      This does not allow to add explanatory annotations to the logically empty result.

        There are no Sub-Tasks for this issue.

            Assignee:
            handl
            Reporter:
            handl
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: