[NETCONF-886] Typo in content parameter error-message Created: 17/Jun/22  Updated: 20/Jun/22  Resolved: 20/Jun/22

Status: Resolved
Project: netconf
Component/s: restconf-nb
Affects Version/s: 3.0.0, 2.0.14, 2.0.16, 3.0.5
Fix Version/s: 4.0.0, 3.0.6

Type: Bug Priority: Low
Reporter: Martin Skorupski Assignee: Peter Puškár
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Priority: 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'.



 Comments   
Comment by Martin Skorupski [ 17/Jun/22 ]

rovarga May I assign this low-prio to you?

Generated at Wed Feb 07 20:16:09 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.