From 2002f15da534a5afdc575699bcc4926faccc9846 Mon Sep 17 00:00:00 2001
From: Ahmed Alaa <92916738+AhmedAlaa4611@users.noreply.github.com>
Date: Mon, 11 Aug 2025 10:07:10 +0300
Subject: [PATCH 1/3] Update middleware.md
---
middleware.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/middleware.md b/middleware.md
index 2ff52e3e7b7..9a8830a02ab 100644
--- a/middleware.md
+++ b/middleware.md
@@ -451,7 +451,7 @@ Route::put('/post/{id}', function (string $id) {
## Terminable Middleware
-Sometimes a middleware may need to do some work after the HTTP response has been sent to the browser. If you define a `terminate` method on your middleware and your web server is using FastCGI, the `terminate` method will automatically be called after the response is sent to the browser:
+Sometimes a middleware may need to do some work after the HTTP response has been sent to the browser. If you define a `terminate` method on your middleware and your web server is using [FastCGI](https://www.php.net/manual/en/install.fpm.php), the `terminate` method will automatically be called after the response is sent to the browser:
```php
Date: Mon, 11 Aug 2025 10:08:20 +0300
Subject: [PATCH 2/3] Update queues.md
---
queues.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/queues.md b/queues.md
index f6a6e873ed6..6be4f74e8d9 100644
--- a/queues.md
+++ b/queues.md
@@ -933,7 +933,7 @@ ProcessPodcast::dispatch($podcast)->withoutDelay();
#### Dispatching After the Response is Sent to the Browser
-Alternatively, the `dispatchAfterResponse` method delays dispatching a job until after the HTTP response is sent to the user's browser if your web server is using FastCGI. This will still allow the user to begin using the application even though a queued job is still executing. This should typically only be used for jobs that take about a second, such as sending an email. Since they are processed within the current HTTP request, jobs dispatched in this fashion do not require a queue worker to be running in order for them to be processed:
+Alternatively, the `dispatchAfterResponse` method delays dispatching a job until after the HTTP response is sent to the user's browser if your web server is using [FastCGI](https://www.php.net/manual/en/install.fpm.php). This will still allow the user to begin using the application even though a queued job is still executing. This should typically only be used for jobs that take about a second, such as sending an email. Since they are processed within the current HTTP request, jobs dispatched in this fashion do not require a queue worker to be running in order for them to be processed:
```php
use App\Jobs\SendNotification;
From 0212c8e9e2774c91af65c415e13e6d345195513c Mon Sep 17 00:00:00 2001
From: Ahmed Alaa <92916738+AhmedAlaa4611@users.noreply.github.com>
Date: Mon, 11 Aug 2025 10:09:20 +0300
Subject: [PATCH 3/3] Update authentication.md
---
authentication.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/authentication.md b/authentication.md
index daa00bd7376..7aa770e6517 100644
--- a/authentication.md
+++ b/authentication.md
@@ -433,7 +433,7 @@ Once the middleware has been attached to the route, you will automatically be pr
#### A Note on FastCGI
-If you are using PHP FastCGI and Apache to serve your Laravel application, HTTP Basic authentication may not work correctly. To correct these problems, the following lines may be added to your application's `.htaccess` file:
+If you are using [PHP FastCGI](https://www.php.net/manual/en/install.fpm.php) and Apache to serve your Laravel application, HTTP Basic authentication may not work correctly. To correct these problems, the following lines may be added to your application's `.htaccess` file:
```apache
RewriteCond %{HTTP:Authorization} ^(.+)$