-
Type: Improvement
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: V4.0_ERRATA02
-
Fix Version/s: V4.0_ERRATA03
-
Component/s: Protocol
-
Labels:None
-
Environment:
Applied
-
Proposal:
-
Resolution:
11.2.6 defines that requests to nullable single-valued navigation properties return 204 No Content if no entity is currently related.
11.2.7 defines that all requests for references to a single entity return 404 Not Found, not distinguishing between "direct" resource paths and resource paths to related entities.
This leads to:
GET Employees('TheBigBoss')/Manager --> 204 No Content
GET Employees('TheBigBoss')/Manager/$ref --> 404 Not Found
Clarify whether this is intentional:
A) Of course, the related Manager is empty, so the reference does not exist, or
B) Ooops, of course both requests should return the same response code because /$ref is just a briefer representation of the non-existing related entity
Also clarify what happens if other path segments are added, e.g. properties or navigation properties:
GET Employees('TheBigBoss')/Manager/Name --> ???
GET Employees('TheBigBoss')/Manager/Department --> ???