OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

odata message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] (ODATA-1609) Data Modification Request succeeds, but response cannot be created


Heiko Theissen created ODATA-1609:
-------------------------------------

             Summary: Data Modification Request succeeds, but response cannot be created
                 Key: ODATA-1609
                 URL: https://issues.oasis-open.org/browse/ODATA-1609
             Project: OASIS Open Data Protocol (OData) TC
          Issue Type: New Feature
          Components: Protocol
            Reporter: Heiko Theissen


Consider a data modification request that requires a response body (for example, creation with {{Prefer: return=representation}} or {{$expand}}). Imagine that the data change is committed to the database, but the subsequent database {{SELECT}} statement fails for some reason.

How shall the server respond to indicate that the data are changed on the database, yet there is no response body?

* 204 No Content plus {{Location}} header after an entity creation
* 204 No Content without {{Preference-Applied: representation}} header after an update with {{Prefer: return=representation}}



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


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]