Why are Guzzle http_errors disabled?

[DrDelay]

I asked this here and decided to open an own issue for it.

They are set to false in the Client and RequestHandler.

I don't really see the reason, especially since the behavior got basically re-implemented in 01cb790.

[Ni42]

Oh, yeah, the nicer way would be to let Guzzle throw them instead of doing that status code check :)

[NicklasWallgren]

Old habits die hard I guess ;) No real reason really, better readability maybe.

[DrDelay]

To inspect/debug errors (e.g. #105) it would be more useful to just let Guzzle handle it I think.

So if there is no real reason why not I'll start looking for what would have to change (removing the then-redundant self-implemented checks).