[NETCONF-663] Get notification streams error Created: 09/Apr/20  Updated: 22/Jul/20  Resolved: 25/May/20

Status: Resolved
Project: netconf
Component/s: restconf-nb
Affects Version/s: Sodium SR1, Sodium SR2
Fix Version/s: Aluminium, Sodium SR3, Magnesium SR2

Type: Bug Priority: Medium
Reporter: wang senxiao Assignee: wang senxiao
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Blocks
blocks INTTEST-83 listening on netconf websocket gives ... Verified
Duplicate
is duplicated by NETCONF-646 Impossible to subscribe to RESTCONF n... Resolved

 Description   

For example,

The expected:

url: http://127.0.0.1:8181/rests/data/ietf-restconf-monitoring:restconf- state/streams/stream=notification/access=JSON//location

response: { "ietf-restconf-monitoring:location": "ws://127.0.0.1:8181/rests/notification-stream/tapi- notification:notification/JSON" }

The actually observed:

url: http://127.0.0.1:8181/rests/data/ietf-restconf-monitoring:restconf- state/streams/stream=notification/access=JSON//location

 

response: <html> <head> <meta http-equiv="Content-Type" content="text/html;charset=utf-8" /> <title>Error 500 Request failed.</title> </head> <body> <h2>HTTP ERROR 500</h2> <p>Problem accessing /rests/data/ietf-restconf-monitoring:restconf- state/streams/stream=notification/access=JSON//location. Reason: <pre> Request failed.</pre> </p> </body> </html>



 Comments   
Comment by wang senxiao [ 15/Apr/20 ]

jluhrsen

ecelgp

rovarga

Have time to look at this problem?

Comment by Jamo Luhrsen [ 29/Apr/20 ]

yes, I will try to get to this sooner or later. Sorry for the delay. I did write a test jira (you can see it above under "blocks").

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