For invalid requests, e.g. with an invalid game value in a game_event request, GameSense returns a 400 error with a {"error":"..."} string (JSON) in the body but the Content-type is text/html instead of application/json.
This issue is made worse by the fact that for 404 errors (e.g when sending a request to /game_event_foo), GameSense returns a 404 error with a simple Page not found string (i.e. not JSON) in the body.
In other words, an app has no way to know if the response should be parsed or not to extract the error message.
For invalid requests, e.g. with an invalid
gamevalue in agame_eventrequest, GameSense returns a 400 error with a{"error":"..."}string (JSON) in the body but theContent-typeistext/htmlinstead ofapplication/json.This issue is made worse by the fact that for 404 errors (e.g when sending a request to
/game_event_foo), GameSense returns a 404 error with a simplePage not foundstring (i.e. not JSON) in the body.In other words, an app has no way to know if the response should be parsed or not to extract the error message.