Handle Errors (404, 500, etc.)

Open codyjames opened this issue 5 years ago • 4 comments

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

Sep 09 '20 20:09 codyjames

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

Sep 09 '20 21:09 codyjames

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

Sep 10 '20 17:09 michaelrog

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

Aug 24 '21 13:08 gixxy22

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

Aug 24 '21 15:08 michaelrog