Fix unparseable data not raised as an error

Created by: stanhu

Previously if an unparsable response were returned with a 200 response, an OAuth2::Error would not be raised even if raised_errors were enabled.

This cleans up and adds tests for this case.

Merge request reports

Loading