[CONTROLLER-671] Restconf returns Status code 409 if list item is not found Created: 08/Aug/14  Updated: 25/Jul/23  Resolved: 15/Aug/14

Status: Resolved
Project: controller
Component/s: restconf
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Tony Tkacik Assignee: Tony Tkacik
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All

Issue Links:
Relates
relates to NETCONF-682 RFC8040 compliance - wrong URI return... Resolved
External issue ID: 1503

 Comments   
Comment by Vratko Polak [ 12/Aug/14 ]

Has https://git.opendaylight.org/gerrit/9893 any drawbacks?

Comment by Vratko Polak [ 13/Aug/14 ]

Response to gerrit comment of Jozef Gloncak.
> Just remark.
> According to
> http://tools.ietf.org/html/draft-bierman-netconf-restconf-02#section-6 (second table)
> data-missing should be mapped to 409 status code

True.
The same section also contains
"The following table summarizes the return status codes used specifically by RESTCONF operations:"
followed by table containing error code 404,
but this error code is NOT present in the mapping table.

My interpretation is that the draft contains typo, and data-missing should really be mapped to code 404, as in the gerrit patch.

How can I submit a patch to the draft document?

Comment by Vratko Polak [ 13/Aug/14 ]

As of now, ODL indeed implements exactly what restconf specification dictates, up to http://tools.ietf.org/html/draft-ietf-netconf-restconf-01
Marking as WONTFIX.
This bug may be re-opened if ever "data-missing" error-tag becomes officially mapped to status code 404.

Generated at Wed Feb 07 19:53:35 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.