[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 ]

Martin Zurmuehl updated ODATA-761:
----------------------------------

    Proposal: 
Actions that create and return a single entity follow the rules for entity creation - must return a location header, should return 201 created unless the return-minimal preference has been specified, in which case the service may return 204 and no content, but still include the location header. 

Applied:
https://www.oasis-open.org/committees/download.php/55616/odata-v4.0-wd08-part1-protocol-2015-05-07.docx

  was:
Actions that create and return a single entity follow the rules for entity creation - must return a location header, should return 201 created unless the return-minimal preference has been specified, in which case the service may return 204 and no content, but still include the location header. 

Applied:
https://www.oasis-open.org/committees/download.php/55613/odata-v4.0-wd08-part1-protocol-2015-05-07.docx


> 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: [Applied]
>            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)