[NETCONF-648] Unable to invoke no-args RPC using apidoc explorer Created: 05/Nov/19  Updated: 10/Jun/20  Resolved: 10/Jun/20

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

Type: Bug Priority: Medium
Reporter: Richard Kosegi Assignee: Jamo Luhrsen
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

RPC with no input arguments can't be invoked using apidocs explorer.

An attempt to do so will result in HTTP 415 (with no payload)

This is equivalent cURL:

curl -v 'http://localhost:8181/restconf/operations/jsonrpc:force-reload' -H 'Accept: application/json' -H 'Content-Type: text/plain;charset=UTF-8' -H 'Authorization: Basic YWRtaW46YWRtaW4=' --data ''

But this one works

curl -v 'http://localhost:8181/restconf/operations/jsonrpc:force-reload' -H 'Accept: application/json' -H 'Content-Type: application/json' -H 'Authorization: Basic YWRtaW46YWRtaW4=' --data ''

Seems like 'Content-Type: text/plain;charset=UTF-8' header is causing issue.

 



 Comments   
Comment by Richard Kosegi [ 09/Mar/20 ]

Maybe related https://github.com/swagger-api/swagger-js/issues/326

Comment by Richard Kosegi [ 06/Jun/20 ]

Problem is not present in master branch with NETCONF-687

Comment by Jamo Luhrsen [ 09/Jun/20 ]

so, do we want to close this or something we might want to still get fixed in Magnesium?

Comment by Richard Kosegi [ 09/Jun/20 ]

I don't think someone will ever fix this. Let's close it then.

Comment by Jamo Luhrsen [ 10/Jun/20 ]

ok, it's closed as "won't do"

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