[NETCONF-634] Restconf can not support create resource by restconf/data Created: 18/Jul/19 Updated: 12/Oct/20 |
|
| Status: | Open |
| Project: | netconf |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Medium |
| Reporter: | wang senxiao | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
Follow the rfc8040, we can create resource by restconf/data to replace retconf/data. for example: POST /restconf/data HTTP/1.1 Host: example.com Content-Type: application/yang-data+json
{ "example-jukebox:jukebox" : {} }
If the resource is created, the server might respond as follows: HTTP/1.1 201 Created Date: Thu, 26 Jan 2017 20:56:30 GMT Server: example-server Location: https://example.com/restconf/data/example-jukebox:jukebox Last-Modified: Thu, 26 Jan 2017 20:56:30 GMT ETag: "b3a3e673be2"
But actually it returns: <html> <head> <meta http-equiv="Content-Type" content="text/html;charset=utf-8"/> <title>Error 404 Not Found</title> </head> <body> <h2>HTTP ERROR 404</h2> <p>Problem accessing /restconf/data/ Reason: <pre> Not Found</pre> </p> </body> </html>
So are we going to implement this way? |