← Prev in month ← Prev in thread
Next in thread → Next in month →

[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

From
OASIS Issues Tracker <>
Date
2014-05-01T04:18:59+00:00
ID
JIRA.23753.1398917928185.306.1398917945428@customer-jira
Thread
[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
Evan Ireland created ODATA-654:
----------------------------------

             Summary: 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
            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)
← Prev in month ← Prev in thread
Next in thread → Next in month →