Snapd API: Curling inexisting endpoint returns TBD result

Bug #2054449 reported by Nathan Teodosio
6
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"
  ]
}
<---

Revision history for this message
Zygmunt Krynicki (zyga) wrote :

I think this is a remnant from very old days :)

Revision history for this message
Nathan Teodosio (nteodosio) wrote :

For the new days GET and POST might be great places for Easter eggs. Just saying. (;

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.