[OASIS Issue Tracker] (ODATA-761) 11.5.4.1 Invoking an Action: Location header for 201 Created responses

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

     [ https://issues.oasis-open.org/browse/ODATA-761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ralf Handl updated ODATA-761:
-----------------------------

    Proposal: 
Create and return single entity: 201 Created with Location header
Create entity/entities and return collection of entities: 200 Ok, no Location header
Any other return type: 200 Ok
No return type: 204 No Content
If the client requests no results with the return preference, the rules of section 8.2.8.7 apply.

  was:
Create and return single entity: 201 Created with Location header
Create and return multiple entities: 200 Ok, no Location header
Any other return type: 200 Ok
No return type: 204 No Content
If the client requests no results with the return preference, the rules of section 8.2.8.7 apply.


> 11.5.4.1 Invoking an Action: Location header for 201 Created responses
> ----------------------------------------------------------------------
>
>                 Key: ODATA-761
>                 URL: https://issues.oasis-open.org/browse/ODATA-761
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData Protocol
>    Affects Versions: V4.0_ERRATA02
>         Environment: [Proposed]
>            Reporter: Ralf Handl
>            Priority: Minor
>             Fix For: V4.0_ERRATA03
>
>
> Section "11.5.4.1 Invoking an Action" specifies that actions creating entities respond with 201 Created. Nothing is mentioned about the location header.
> For consistency with section "11.4.2 Create an Entity" actions that create and return a single entity MUST also send a Location header to allow referencing the newly created entity with a content-id within batch requests.
> Section "11.7.3.1 Referencing New Entities in a Change Set" has to be reformulated to also cover new entities created by actions.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)