Handle Errors (404, 500, etc.)

[codyjames]

Currently if the scraper gets a 404 or 500 it kills the whole page in a way that isn't recoverable.

[codyjames]

I resolved this by switching to the Symfony client which is more resilient.

[michaelrog]

Nice. I'm gonna leave this issue open, with the intention of handing errors more gracefully in production.

[gixxy22]

switching to Symfony doesnt solve this unfortunately if the page times out.

[michaelrog]

The http_errors request option prevents Guzzle from throwing an exception if it encounters an HTTP error (40X, 50X).