Guzzle Error Message gets truncated

Try using the getBody() method on the response.

dd($response->getBody());

Thanks for your reply @JoeDawson ! However, I can't because, the exception is thrown.

I do it like this

 $response = $client->post($this->url, [myparameters]

Which throws the exception, so in

 $response = $client->post($this->url, [myparameters]
dd($response->getBody());

the dd part is never executed.

Or am I thinking not correct here?

Sorry, you'll need a try catch I guess. You could try this:

try {
    $response = $client->post($this->url, $params);
} catch(Exception $e) {
    dd($e->getBody());
}

You may need to replace the caught exception with the one Guzzle throws if it differs from the above.

I am using a try/catch already - but strange, for both Exception and the \GuzzleHttp\Exception\ClientException there is no getBody() method.

I have setup XDebug now and I am debugging the Guzzle call step by step, lets see if that helps!

Ah, odd! Best of luck :)

I found the error - I changed some variables from env() to config() (according to 5.2 upgrade notes) and for whatever reason one setting didnt quite workout, turned out to be NULL and this was it. I would have never found out without XDebug - I like it now, really! :D

Thanks for your help @JoeDawson anyway :)

Good night Andreas

Well, after I fixed this, of course the next error happend with this bloody amazon API and the error messages where truncated again.

After debugging for a while I finally found a way how to get the whole XML error message from the API:

            } catch (\GuzzleHttp\Exception\ClientException $e) {

                ddd($e->getResponse()->getBody()->getContents());

            }

The trick was to get the Response Object first, then via the getContents method you can access the stream with the whole XML in it.

Heureka!

Thanks for that andreasb. Was having the same problem with a simple mailchimp integration - error messages being truncated. That worked a treat.

@andreasb your reply was very helpful! :D

You can also set the 'http_errors' request option to false in Guzzle to skip the Try / Catch altogether.

@andreasb thank you

To build on @PlayIt 's answer, you can do this:

$client = new Client;

        $response = $client->post('http://127.0.0.1:8000/documents', [
            'json' => [
                "user_id" => 1
            ],
            "http_errors" => false,
        ]);
        dd($response->getBody()->getContents());

Not so much of an answer, but a hint because I had the same problem, until I realized there was several more piles of errors on top of the one that is all pretty printed in HTML and last in the list in the text login file on the server. Just look directly above the last error in the log file and so on and so forth. I had about 4.

@ANDREASB - Saved me so much time... Thanks!

I solved the problem by catching BadResponseException instead of ClientException with the same logic and it worked perfect. BadResponseException is the superclass for Guzzle exceptions

I did something very adventurous. I modified guzzel's exception handler

guzzel on purpose only reads up 120 bytes of info and prints truncated next to it.

The file is located at : /vendor/guzzlehttp/guzzle/src/Exception/RequestException.php

So I modified that function and below is what my function looks like:

public static function getResponseBodySummary(ResponseInterface $response) { $body = $response->getBody();

    if (!$body->isSeekable() || !$body->isReadable()) {
        return null;
    }

    $size = $body->getSize();

    if ($size === 0) {
        return null;
    }

    // Matches any printable character, including unicode characters:
    // letters, marks, numbers, punctuation, spacing, and separators.
    if (preg_match('/[^\pL\pM\pN\pP\pS\pZ\n\r\t]/', $body)) {
        return null;
    }

    return $body;
    
}

Awesome :) thanks @andreasb

Дякую @andreasb Thanks @andreasb