[NETCONF-799] Restconf throws error for action with no output Created: 06/Aug/21 Updated: 09/Aug/21 Resolved: 09/Aug/21 |
|
| Status: | Resolved |
| Project: | netconf |
| Component/s: | restconf-nb |
| Affects Version/s: | None |
| Fix Version/s: | 1.13.4, 2.0.3 |
| Type: | Bug | Priority: | Medium |
| Reporter: | Ivan Hrasko | Assignee: | Ivan Hrasko |
| Resolution: | Done | Votes: | 0 |
| Labels: | pt | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
Restconf throws an error when there is no output for the invoked action. But actions with no output are absolutely legal and according to RFC 8040 (section: 3.6. Operation Resource): "If the RPC operation is invoked without errors and if the "rpc" or "action" statement has no "output" section, the response message MUST NOT include a message-body and MUST send a "204 No Content" status-line instead." |
| Comments |
| Comment by Ivan Hrasko [ 06/Aug/21 ] |
|
Now, no exception is thrown and response with no body and status code 204 is returned in case action has succeeded and has no output. |