[NETCONF-632] Rest endpoints for POST request on rpc/action having No Input data is stopped at Rest UI with 415 Error Response Code. Created: 11/Jul/19 Updated: 22/Aug/19 Resolved: 22/Aug/19 |
|
| Status: | Resolved |
| Project: | netconf |
| Component/s: | restconf-nb |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Medium |
| Reporter: | Ajay Deep Singh | Assignee: | Ajay Deep Singh |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
Rest endpoint for POST request like the one below with No input payload is blocked at UI for rps/action call with 415 Error no content, which should not be the case reason for rpc/action can have Yang model with just output to be requested from Netconf Server/Node. POST Request : /rests/operations/network-topology:network-topology/topology=topology-netconf/node=pnf-simulator/yang-ext:mount/turing-machine:run
The Same Post |
| Comments |
| Comment by Ajay Deep Singh [ 21/Aug/19 ] |
|
When RESTCONF is presented with empty input, it should create the appropriate empty container – it has the proper context looked up, so can create it accurately and easily. Closing this issue, Code is working as expected. |
| Comment by Ajay Deep Singh [ 21/Aug/19 ] |
|
Code Updates Not required. |
| Comment by Ajay Deep Singh [ 22/Aug/19 ] |
|
Not an issue. Need to provide empty input in RESTCONF |