-
New Feature
-
Resolution: Done
-
Medium
-
None
-
manual testing
Both RFC8040 [0] and draft 18 [1] define Root Resource Discovery mechanism. Neither Draft18 in Nitrogen snapshots, not rfc8040 in oxygen snapshots seem to have that implemented.
$ curl -v -u admin:admin -H "Accept:application/xrd+xml" http://127.0.0.1:8181/.well-known/host-meta * Trying 127.0.0.1... * TCP_NODELAY set * Connected to 127.0.0.1 (127.0.0.1) port 8181 (#0) * Server auth using Basic with user 'admin' > GET /.well-known/host-meta HTTP/1.1 > Host: 127.0.0.1:8181 > Authorization: Basic YWRtaW46YWRtaW4= > User-Agent: curl/7.52.1 > Accept:application/xrd+xml > < HTTP/1.1 404 Not Found < Content-Type: text/html; charset=ISO-8859-1 < Cache-Control: must-revalidate,no-cache,no-store < Content-Length: 305 < <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 /.well-known/host-meta. Reason: <pre> Not Found</pre></p><hr><i><small>Powered by Jetty://</small></i><hr/> </body> </html> * Curl_http_done: called premature == 0 * Connection #0 to host 127.0.0.1 left intact
[0] https://tools.ietf.org/html/rfc8040#section-3.1
[1] https://tools.ietf.org/html/draft-ietf-netconf-restconf-18#section-3.1
- is duplicated by
-
-
- Resolved
-
-
NETCONF-739 RFC8040 compliance: Root Resource Discovery
-
- Resolved
-
- relates to
-
-
- Resolved
-
