noticed while working on #15916, we do a request that, when successful, returns a 204 response (with no content) currently the client will fail to parse the contents of the response and return an error "response: unexpected end of JSON input, body" even if the request was succesful.
2 lines
95 B
Plaintext
2 lines
95 B
Plaintext
* improve the HTTP client used by `fleetctl` and `fleetd` to prevent errors for 204 responses.
|