Treat [200...399] status code range as errors

This release fixes a bug that didn't treat responses with status codes outside the [200...399] range as errors. Thanks to @davideicardi for reporting it.