{"action":"opened","issue":{"url":"https://api.github.com/repos/freelawproject/recap/issues/95","labels_url":"https://api.github.com/repos/freelawproject/recap/issues/95/labels{/name}","comments_url":"https://api.github.com/repos/freelawproject/recap/issues/95/comments","events_url":"https://api.github.com/repos/freelawproject/recap/issues/95/events","html_url":"https://github.com/freelawproject/recap/issues/95","id":68837421,"number":95,"title":"[CLOSED] Ignore invalid JSON in responses to requests for it.","user":{"login":"freelawbot","id":8268044,"avatar_url":"https://avatars.githubusercontent.com/u/8268044?v=3","gravatar_id":"","url":"https://api.github.com/users/freelawbot","html_url":"https://github.com/freelawbot","followers_url":"https://api.github.com/users/freelawbot/followers","following_url":"https://api.github.com/users/freelawbot/following{/other_user}","gists_url":"https://api.github.com/users/freelawbot/gists{/gist_id}","starred_url":"https://api.github.com/users/freelawbot/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/freelawbot/subscriptions","organizations_url":"https://api.github.com/users/freelawbot/orgs","repos_url":"https://api.github.com/users/freelawbot/repos","events_url":"https://api.github.com/users/freelawbot/events{/privacy}","received_events_url":"https://api.github.com/users/freelawbot/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-04-16T03:41:43Z","updated_at":"2015-04-16T03:41:43Z","closed_at":null,"body":"<a href=\"https://github.com/audiodude\"><img src=\"https://avatars.githubusercontent.com/u/57832?v=3\" align=\"left\" width=\"96\" height=\"96\" hspace=\"10\"></img></a> **Issue by [audiodude](https://github.com/audiodude)**\n_Wednesday Mar 25, 2015 at 02:58 GMT_\n_Originally opened as https://github.com/freelawproject/recap-chrome/pull/8_\n\n----\n\nThe real problem that causes #2 is that the server is not returning JSON to a JSON request. Presumably because the server considers it an error.\r\n\r\nThis PR attempts to fix this by just aborting the ready state change function and not calling the callback. It is assumed that the caller was expecting a parsed JSON data structure and since we are unable to provide that, the callback should be skipped.\r\n\r\nTo be clear, this simply sidesteps the issue and avoids the stack trace in the console. We still need to investigate why the server is returning such a response and if there is a more appropriate action the extension can take.\n\n----\n\n_**[audiodude](https://github.com/audiodude)** included the following code: https://github.com/freelawproject/recap-chrome/pull/8/commits_\n"}}