Centralize HTTP Client Configuration with Laravel's globalOptions Method
Last updated on by Harris Raftopoulos

Laravel introduces the globalOptions method to simplify HTTP client configuration across your application. This feature creates a central point for defining default HTTP client behavior, reducing code duplication while maintaining consistent standards.
Working with multiple external APIs often requires setting the same timeouts, headers, or other configuration options repeatedly. Laravel's HTTP client now allows developers to establish these settings globally, creating a consistent foundation for all requests:
use Illuminate\Support\Facades\Http; // Set global options in a service providerHttp::globalOptions([ 'timeout' => 5, 'connect_timeout' => 2,]);
After configuration, these options automatically apply to all HTTP requests made through Laravel's HTTP client, unless specifically overridden for individual requests.
This approach particularly benefits applications interacting with numerous third-party services. Here's how you might implement global configuration in a service provider:
<?php namespace App\Providers; use Illuminate\Support\Facades\Http;use Illuminate\Support\ServiceProvider; class AppServiceProvider extends ServiceProvider{ /** * Bootstrap any application services. */ public function boot(): void { Http::globalOptions([ // Set reasonable timeouts 'timeout' => 8, 'connect_timeout' => 3, // Add default headers 'headers' => [ 'User-Agent' => 'ShoppingPortal/2.1', 'Accept' => 'application/json', ], // Configure default retry behavior 'retry' => 2, 'retry_delay' => 150, ]); }}
While the global settings establish defaults, you maintain flexibility by overriding specific options when needed:
// Uses global options plus specific ones for this requestHttp::withToken('payment-gateway-token') ->post('https://payments.example.com/process', [ 'amount' => 99.95, 'currency' => 'USD' ]); // Override timeout just for this requestHttp::timeout(25) ->get('https://inventory.example.com/stock-check');
Remember that calling globalOptions multiple times completely replaces previous configurations rather than merging with them. Organize your service provider setup to ensure all global options appear in a single configuration call for maximum clarity and predictability.