Snapd API: Curling inexisting endpoint returns TBD result
Bug #2054449 reported by
Nathan Teodosio
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
snapd |
New
|
Undecided
|
Unassigned |
Bug Description
By forgetting the -X flag to Curl I discovered a weird behavior in the API. It will always return a TBD result whatever the inexisting endpoint one tries to access.
--->
% curl -sS GET --unix-socket /run/snapd.socket | jq .
{
"type": "sync",
"status-code": 200,
"status": "OK",
"result": [
"TBD"
]
}
<---
To post a comment you must log in.
I think this is a remnant from very old days :)