How to Make an Internal Request in Laravel

There are times when you want to develop and use a single request API, rather than working with Livewire or calling a function directly. For example, when you’re building a frontend with Blade or Livewire, instead of calling a function from the controller, you can turn the function’s features into an API and handle things by making an internal request from the controller. The downside is that a call still occurs internally! The advantage is that you can manage and develop everything through a single API. Later, you can simply hand the API over to additional developers, whether they’re working on Blade or another frontend, so they can build a redesigned frontend. Although I’m building the service by myself, if I consider its potential, scalability, and maintainability, the disadvantage is no longer really a disadvantage. That’s because if I later want to push the service forward after seeing its potential, additional development staff will be essential. In that case, if you develop using the internal request call (API) approach, you can immediately build additional frontend functionality using the API without changing anything. Of course, if you separated the frontend and backend into separate projects from the very start, there’s no need to do this. ```php use Illuminate\Container\Container; use Illuminate\Http\Request; public function internalRequest(Request $request, string $uri, string $method): Response { $req = Request::create( $uri, $method, $request->all(), $request->cookie(), [], $request->server() ); $req->headers->set('token', 'test'); return Route::dispatch($req); return Container::getInstance()->handle($req); } ``` This approach doesn’t make an actual HTTP request. Since the request is made inside the Laravel application, no actual HTTP request occurs. Additional notes — 24.10.17 The problem with using the Route::dispatch() approach above is that it doesn’t pass through the web or API middleware. The strange thing is that the API middleware doesn’t run, but the web middleware does, because it’s enabled by default. So, when you need to handle things like authentication using cookies or headers, the code below will solve the problem. (The code below also uses all route middleware.) ```php return Container::getInstance()->handle($req); return app()->handle($req); ``` You need to use these two options for the request to pass through the middleware as well!

More posts