https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/CONTROLLER-671 controller <p>Operating System: All<br/> Platform: All</p> CONTROLLER-671

Restconf returns Status code 409 if list item is not found

Bug Resolved Done Tony Tkacik Tony Tkacik Fri, 8 Aug 2014 08:40:15 +0000 Tue, 25 Jul 2023 08:24:03 +0000 Fri, 15 Aug 2014 17:23:18 +0000 restconf 0 5 <p>Has <a href="https://git.opendaylight.org/gerrit/9893" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/9893</a> any drawbacks?</p> <p>Response to gerrit comment of Jozef Gloncak.<br/> &gt; Just remark.<br/> &gt; According to<br/> &gt; <a href="http://tools.ietf.org/html/draft-bierman-netconf-restconf-02#section-6" class="external-link" target="_blank" rel="nofollow noopener">http://tools.ietf.org/html/draft-bierman-netconf-restconf-02#section-6</a> (second table)<br/> &gt; data-missing should be mapped to 409 status code</p> <p>True.<br/> The same section also contains<br/> "The following table summarizes the return status codes used specifically by RESTCONF operations:"<br/> followed by table containing error code 404,<br/> but this error code is NOT present in the mapping table.</p> <p>My interpretation is that the draft contains typo, and data-missing should really be mapped to code 404, as in the gerrit patch.</p> <p>How can I submit a patch to the draft document?</p> <p>As of now, ODL indeed implements exactly what restconf specification dictates, up to <a href="http://tools.ietf.org/html/draft-ietf-netconf-restconf-01" class="external-link" target="_blank" rel="nofollow noopener">http://tools.ietf.org/html/draft-ietf-netconf-restconf-01</a><br/> Marking as WONTFIX.<br/> This bug may be re-opened if ever "data-missing" error-tag becomes officially mapped to status code 404.</p> Relates NETCONF-682 Development External issue ID 1503 External issue URL ODL SR Target Milestone Rank 0|i02lu7: