Understanding Laravel Request Instantiation and Its Symfony Foundations

In Laravel, after the initial setup, the framework instantiates a request object. A request is the HTTP message sent by a client, consisting of a request line, headers, and a body. Laravel stores this data in an instance of the Illuminate\Http\Request class, and the request is created via the static capture() method ( $request = Illuminate\Http\Request::capture(); ).

Laravel heavily leverages components from the Symfony framework, following the open‑source principle of not reinventing the wheel. By reusing Symfony’s well‑designed modules, Laravel benefits from PSR standards and Composer. The Laravel request object builds upon Symfony’s request, which is created by the static createFromGlobals() method (see vendor/symfony/http-foundation/Request.php ).

Symfony creates a request by passing PHP’s superglobal arrays ($_GET, $_POST, $_COOKIE, $_FILES, $_SERVER) to a request factory. It first normalises certain $_SERVER entries because of a PHP bug that stores Content‑Type and Content‑Length in HTTP_CONTENT_TYPE and HTTP_CONTENT_LENGTH when running under the cli‑server SAPI.

If a custom request factory is defined, its method is assigned to the $requestFactory property; otherwise, the request is instantiated via new static , which follows PHP’s late static binding rules.

Request data is encapsulated in classes such as ParameterBag and FileBag . These classes inherit from ParameterBag , providing a uniform storage mechanism while adding specialised handling functions for files and server parameters.