I am noticing the difference in the RESTCONF "GET" response if the service does not exist in the CDB. The older NSO version (5.3.4.1) was returning different results than what we are seeing in the current NSO version (5.7.5.1). Can someone tell me what the correct response is? If this was a defect in the 5.3.x release, then in which release did this get fixed?
Sample requests
================
//NSO 5.7.5.1
[root@user]# curl -kiu xxx:xxxxx https://xxxxxxxx/restconf/data/service-path=keys?depth=unbounded&with-defaults=report-all&content=config -X GET -H "accept: application/yang-data+json"
HTTP/1.1 404 Not Found
Date: Wed, 15 Mar 2023 07:16:14 GMT
Cache-Control: private, no-cache, must-revalidate, proxy-revalidate
Content-Length: 197
Content-Type: application/yang-data+json
X-Cisco-NSO-Trace-ID: 9c1a9ca9-ec82-44d0-9523-09dcf22929a8
Pragma: no-cache
Content-Security-Policy: default-src 'self'; block-all-mixed-content; base-uri 'self'; frame-ancestors 'none';
Strict-Transport-Security: max-age=15552000; includeSubDomains
X-Content-Type-Options: nosniff
X-Frame-Options: DENY
X-XSS-Protection: 1; mode=block
{
"ietf-restconf:errors": {
"error": [
{
"error-type": "application",
"error-tag": "invalid-value",
"error-message": "uri keypath not found"
}
]
}
}
//NSO 5.3.4.1
[root@user]# curl -kiu xxx:xxxxx https://xxxxxxxx/restconf/data/service-path=keys?depth=unbounded&with-defaults=report-all&content=config -X GET -H "accept: application/yang-data+json"
HTTP/1.1 404 Not Found
Date: Wed, 15 Mar 2023 07:11:32 GMT
Cache-Control: private, no-cache, must-revalidate, proxy-revalidate
Content-Length: 0
Content-Type: text/html; charset=UTF-8
Pragma: no-cache
Content-Security-Policy: default-src 'self'; block-all-mixed-content; base-uri 'self'; frame-ancestors 'none';
Strict-Transport-Security: max-age=15552000; includeSubDomains
X-Content-Type-Options: nosniff
X-Frame-Options: DENY
X-XSS-Protection: 1; mode=block
