Currently, when sending a
/queries/entity/somequery/count request, the response has a content-type of
text/plain, whilst it should be
From a client point of view, API responses should be consistent with the overall purpose/surface of the API itself (or part of it). Or, alternatively, the API itself should support
Accept request headers to select the appropriate content-type for the response.
The purpose of the entire
queries resource endpoint (and in same regard the
entities one) is to return data serialized in JSON representation.
text/plain response, containing a valid JSON value (it is a plain
number), is a violation of such contract.