Clarify exclusions for fallback HTTP error pages (#9701)

weshooper · taylorotwell · web-flow · commit 329323efb2a0 · 2024-06-12T09:05:37.000-05:00
* Clarify exclusions for fallback HTTP error pages

* Update errors.md

---------

Co-authored-by: Taylor Otwell &lt;taylor@laravel.com&gt;
diff --git a/errors.md b/errors.md
@@ -410,4 +410,6 @@ php artisan vendor:publish --tag=laravel-errors
 <a name="fallback-http-error-pages"></a>
 #### Fallback HTTP Error Pages
 
-You may also define a "fallback" error page for a given series of HTTP status codes. This page will be rendered if there is not a corresponding page for the specific HTTP status code that occurred. To accomplish this, define a `4xx.blade.php` template and a `5xx.blade.php` template in your application's `resources/views/errors` directory.
+You may also define a "fallback" error page for a given series of HTTP status codes. This page will be rendered if there is not a corresponding page for the specific HTTP status code that occurred. To accomplish this, define a `4xx.blade.php` template and a `5xx.blade.php` template in your application's `resources/views/errors` directory. 
+
+When defining fallback error pages, the fallback pages will not affect `404`, `500`, and `503` error responses since Laravel has internal, dedicated pages for these status codes. To customize the pages rendered for these status codes, you should define a custom error page for each of them individually.
