[NETCONF-119] Unable to get data by keyvalue with "=" Created: 06/Jan/16  Updated: 15/Mar/19  Resolved: 19/Aug/16

Status: Resolved
Project: netconf
Component/s: restconf-nb
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: geyubo Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issue Links:
Blocks
is blocked by NETCONF-18 Enhance RESTconf to implement latest ... Resolved
External issue ID: 4884

 Description   

RESTCONF Protocol draft-ietf-netconf-restconf-09

Examples:

container top {
list list1 {
key "key1 key2 key3";
...
list list2 {
key "key4 key5";
...
leaf X

{ type string; }

}
}
}
For the above YANG definition, URI with key leaf values will be
encoded as follows (line wrapped for display purposes only):
/restconf/data/example-top:top/list1=key1val,key2val,key3val/
list2=key4val,key5val/X

The following example shows how reserved characters are percent-
encoded within a key value. The value of "key1" contains a comma,
single-quote, double-quote, colon, double-quote, space, and forward
slash. (,'":" /). Note that double-quote is not a reserved
characters and does not need to be percent-encoded. The value of
"key2" is the empty string, and the value of "key3" is the string
"foo".

Example URL:

/restconf/data/example-top:top/list1=%2C%27"%3A"%20%2F,,foo



 Comments   
Comment by Martin Ciglan [ 07/Jan/16 ]

This support is expected in Boron, when
https://bugs.opendaylight.org/show_bug.cgi?id=2781
will be implemented.

I'm moving this issue to Netconf project.

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