A non-JSON response would throw an ugly JSON parse error and stack trace would point inside of the module. (encountered this when getting a 404 from tumblr.)
Added try/catch around the json parsing of the response, and returning "Invalid Response" as the error when non-json response is encountered.
catching json parse errors and returning 'Invalid Response' Error whe…
…n non-json response is returned.
Fix #2 issue