Weave Code
Http Kernel Laravel Package
symfony/http-kernel
The Symfony HttpKernel component converts a Request into a Response through a structured process built on the EventDispatcher, and is flexible enough to power full-stack frameworks, micro-frameworks, or advanced CMS systems like Drupal.
Provides a structured process for converting a Request into a Response
Frequently asked questions about Http Kernel
- What is symfony/http-kernel and what does it do?
- symfony/http-kernel is the Symfony component that converts an HTTP Request into a Response through a structured, event-driven process. It provides the KernelInterface, controller resolution, argument resolution, exception handling, and lifecycle events such as kernel.request and kernel.response. Laravel already depends on parts of Symfony's HTTP stack, so the component is familiar to many Laravel applications even when used indirectly.
- How do I install symfony/http-kernel in a Laravel project?
- Install it with Composer using composer require symfony/http-kernel. In most Laravel apps you will not need to install it directly because Laravel pulls in Symfony HTTP components through its own dependencies. If you are building a custom kernel or using HttpCache or sub-requests, add the package explicitly and match the Symfony version required by your Laravel release.
- Is symfony/http-kernel compatible with Laravel?
- Yes, it is highly compatible because Laravel uses Symfony HttpFoundation, EventDispatcher, and HttpKernelInterface under the hood. You can adopt KernelInterface, controller resolvers, and event listeners alongside Laravel's middleware pipeline. The main work is bridging Laravel's Illuminate kernel with a custom Symfony kernel and avoiding event-name collisions.
- Which Laravel and Symfony versions does symfony/http-kernel support?
- Version support follows Symfony's release lines, and your Laravel version determines the compatible range. Laravel 10 and later typically align with Symfony 6.4 through newer 7.x releases, so check composer constraints before upgrading. Pin symfony/http-kernel to a version that matches your Laravel framework's Symfony dependencies to avoid conflicts.
- How does Symfony HttpKernel differ from Laravel's HTTP kernel?
- Laravel's HTTP kernel is an opinionated implementation built on Symfony's HttpKernelInterface, with bootstrapping, middleware groups, and service container integration. Symfony HttpKernel is a lower-level abstraction focused on the request-to-response lifecycle, events, and controller resolution. Use Laravel's kernel for normal app requests and Symfony HttpKernel when you need custom kernel behavior or reusable HTTP processing outside Laravel's default flow.
- Can I use Symfony HttpKernel for sub-requests in Laravel?
- Yes, Symfony HttpKernel provides sub-request handling through HttpKernel::handle() with a Request object and a kernel type such as HttpKernelInterface::SUB_REQUEST. This is useful for API composition, embedding controller output, or fragment rendering. In Laravel, you should carefully scope sub-requests and avoid deep recursion or excessive nested requests because they add overhead and can complicate debugging.
- How do Symfony HttpKernel events interact with Laravel middleware and events?
- Symfony HttpKernel dispatches lifecycle events like kernel.request, kernel.controller, kernel.response, and kernel.exception through EventDispatcher. Laravel's middleware and events are separate but can coexist, so use unique event names or namespaces to prevent collisions. You can add Symfony event listeners for cross-cutting concerns such as logging or caching while keeping Laravel middleware for application-level concerns.
- Can I use Symfony HttpKernel's HttpCache with Laravel's cache drivers?
- Yes, Symfony's HttpCache can be used with Laravel's cache stores when you configure a compatible store adapter. It is most useful for reverse-proxy-style caching, edge caching, or fragment caching where you control cache invalidation. For typical Laravel caching, built-in Cache::remember() and cache tags may be simpler, so evaluate whether HttpCache adds real value.
- How should I test a custom Symfony HttpKernel implementation in Laravel?
- Test custom kernels with Symfony's HttpKernel test utilities and Laravel's HTTP testing helpers where possible. Use functional tests that dispatch real Request objects through your kernel and assert on Response status, headers, and content. Also test event listeners and exception paths, and isolate sub-request behavior to catch recursion or cache-related issues.
- What are the production risks and alternatives to using symfony/http-kernel with Laravel?
- Production risks include event-listener conflicts, cache invalidation complexity, debugging overhead, and version drift between Laravel and Symfony dependencies. Mitigate them by pinning compatible versions, using unique event namespaces, adding integration tests, and monitoring Symfony releases. If you only need middleware or caching, Laravel's built-in features may be a simpler alternative to a custom HttpKernel integration.
Weaver
How can I help you explore Laravel packages today?