[OASIS Issue Tracker] (ODATA-654) OData-EntityId is only required for 204 No Content, but client may need it when server doesn't support canonical URLs

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

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

Michael Pizzo updated ODATA-654:
--------------------------------

    Environment: [Applied]  (was: [Proposed])

> OData-EntityId is only required for 204 No Content, but client may need it when server doesn't support canonical URLs
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: ODATA-654
>                 URL: https://tools.oasis-open.org/issues/browse/ODATA-654
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData Protocol 
>    Affects Versions: V4.0_OS
>         Environment: [Applied]
>            Reporter: Evan Ireland
>            Priority: Minor
>             Fix For: V4.0_ERRATA01
>
>
> OData protocol section "8.3.3 Header OData-EntityId" states:
> "A response to a create operation that returns 204 No Content MUST include an OData-EntityId response header."
> If the server doesn't support canonical URLs, the client cannot obtain the entity id of a created entity (when 204 No Content is returned) without requerying the entity.



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