How to correcly use Exceptions::dontTruncateRequestExceptions() ?

[sanfair]

I have a hard time understanding how to make it work properly.

Quote from docs:

By default, RequestException messages are truncated to 120 characters when logged or reported. To customize or disable this behavior, you may utilize the truncateRequestExceptionsAt and dontTruncateRequestExceptions methods when configuring your application's exception handling behavior in your bootstrap/app.php file:

bootstrap/app.php

<?php

declare(strict_types=1);

use Illuminate\Foundation\Application;
use Illuminate\Foundation\Configuration\Exceptions;

return Application::configure(basePath: dirname(__DIR__))
  ->withExceptions(static function (Exceptions $exceptions): void {
      $exceptions->dontTruncateRequestExceptions();
  })->create();

routes/web.php

<?php

declare(strict_types=1);

\Illuminate\Support\Facades\Route::get('/test', static function () {
  \Illuminate\Support\Facades\Http::baseUrl('https://google.com')
      ->get('/not-found')
      ->throw()
      ->dump();
});

Result

In the example above, execution will happen in the following order:

1. App bootstrap
2. \Illuminate\Foundation\Configuration\ApplicationBuilder::withExceptions() which stores a callable that will be executed after resolving \Illuminate\Foundation\Exceptions\Handler
3. Route execution
4. Request to 3rd party API
5. \Illuminate\Http\Client\Response::throw()
6. \Illuminate\Http\Client\Response::toException()
7. \Illuminate\Http\Client\RequestException::prepareMessage() <--- truncates response body
8. \Illuminate\Foundation\Exceptions\Handler::__construct()
9. afterResolving callbacks for \Illuminate\Foundation\Exceptions\Handler (callable passed to ApplicationBuilder::withExceptions())
10. \Illuminate\Foundation\Configuration\Exceptions::dontTruncateRequestExceptions() <--- configuration for RequestException to not truncate response body

What is the point of that configuration if that call will happen only after the response has already been truncated?

Am I missing how to use it correctly?

[bugraskl]

You are not using the API incorrectly. On the affected Laravel 12 releases this was a framework lifecycle issue: the RequestException message could be prepared before the exception configuration callback called dontTruncateRequestExceptions().

The framework fix is in laravel/framework#57759, linked from issue #57601. The preferred solution is therefore to upgrade to a Laravel framework release containing that fix.

If you must remain on an affected release, call the underlying static setting earlier, for example in AppServiceProvider::boot():

use Illuminate\Http\Client\RequestException;

public function boot(): void
{
    RequestException::dontTruncate();
}

That runs before application code normally sends HTTP requests, avoiding the ordering problem. If the application uses long-lived workers such as Octane or queue workers, restart them after making the change.

[Icaro0310]

It goes inside the withExceptions callback in bootstrap/app.php:

->withExceptions(function (Exceptions $exceptions) {
    $exceptions->dontTruncateRequestExceptions();
    // or a custom length instead:
    // $exceptions->truncateRequestExceptionsAt(500);
})

One thing that tripped me up: this only applies to Illuminate\Http\Client\RequestException — i.e. exceptions thrown by Laravel's HTTP client (Http::get(...)->throw() etc.), where the response body is embedded in the exception message. It doesn't affect truncation of other exception messages or logs.

Also note it only changes what gets reported/logged; the exception message itself is the same. If it's still truncated after configuring, make sure you're on a version that has the method (added in 11.x) and that the exception you're inspecting is actually an HTTP client RequestException.

—
Check out my Repositories: github.com/Icaro0310 · Website: icaro0310.github.io