Details
-
Bug
-
Status: Resolved
-
Low
-
Resolution: Done
-
3.0.0, 2.0.14, 2.0.16, 3.0.5
-
None
-
Low
Description
RFC8040 section 4.8.1 specifies as url 'content' parameter the value 'nonconfig'.
In case the wrong value 'non-config' is used, an error '400 Bad Request' is returned - which is correct. Just the returned error message is misleading:
curl "http:/localhost:8181/rests/data/network-topology:network-topology/topology=topology-netconf/node=after-disaster/yang-ext:mount/tapi-common:context?content=non-config" -u "admin:admin" { "errors": { "error": [ { "error-tag": "invalid-value", "error-info": "Value can be 'all', 'config' or 'non-config', not 'non-config'", "error-message": "Invalid content value: Value can be 'all', 'config' or 'non-config', not 'non-config'", "error-type": "protocol" } ] }
Please correct the error-info and error-message text and list 'nonconfig' as valid parameter, instead of 'non-config'.