-
|
Is there anything that would prevent requests that return a 4xx status code from being processed? I'm noticing that in the event that I get back a 401 or 417 response code from a request, it never makes it to the parse method. Logging shows that the request is indeed being fired but inspection of the parse method shows that it's never called for any response that has a status code of 400 or above. Any ideas why that might be happening? I'd like to be able to handle them properly. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
After some digging around the Guzzle documentation, it became clear that Guzzle handles 4xx responses slightly differently. You'll need to pass into the Request options parameter |
Beta Was this translation helpful? Give feedback.
-
|
Just to highlight the relevant documentation. https://docs.guzzlephp.org/en/stable/request-options.html#http-errors |
Beta Was this translation helpful? Give feedback.
After some digging around the Guzzle documentation, it became clear that Guzzle handles 4xx responses slightly differently.
You'll need to pass into the Request options parameter
'http_errors' => falsein order to see these responses and handle them yourself.