[NETCONF-301] create-data-change-event-subscription response is not in XML format despite request was "application/xml" Created: 20/Oct/16 Updated: 06/Dec/22 Resolved: 06/Dec/22 |
|
| Status: | Resolved |
| Project: | netconf |
| Component/s: | restconf-nb |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Juraj Veverka | Assignee: | Ivan Hrasko |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | pt | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Attachments: |
|
| External issue ID: | 6994 |
| Description |
|
following "Change event notification subscription" procedure on odl wiki https://wiki.opendaylight.org/view/OpenDaylight_Controller:MD-SAL:Restconf:Change_event_notification_subscription setup environment: when I send create-data-change-event-subscription request (see postman collection) with Content-Type "application/xml" response is in JSON format request: response: } |
| Comments |
| Comment by Juraj Veverka [ 20/Oct/16 ] |
|
Attachment openstack.postman_collection.json has been added with description: postman collection |
| Comment by Ivan Hrasko [ 06/Dec/22 ] |
|
In the Netconf version 5 the request looks like: POST http://localhost:8181/rests/operations/sal-remote:create-data-change-event-subscription with the payload: <input xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:remote"> <path xmlns:a="urn:TBD:params:xml:ns:yang:network-topology">/a:network-topology</path> <datastore xmlns="urn:sal:restconf:event:subscription">CONFIGURATION</datastore> <scope xmlns="urn:sal:restconf:event:subscription">BASE</scope> </input> and the result depends on the Accept header not Content-Type! With Accept set to application/xml we successfully get:
<output xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:remote">
<stream-name>data-change-event-subscription/network-topology:network-topology/datastore=CONFIGURATION/scope=BASE</stream-name>
</output>
|
| Comment by Ivan Hrasko [ 06/Dec/22 ] |
|
The issue in not present. User has misconfigured his request (used wrong header parameter). |