Merge pull request #6963 from kenjis/fix-docs-auto-routing

docs: update auto routing notes

Author: kenjis

user_guide_src/source/cli/cli_controllers.rst

@@ -41,8 +41,8 @@ works exactly like a normal route definition:
 
 For more information, see the :ref:`Routes <command-line-only-routes>` page.
 
-.. warning:: If you enable :ref:`auto-routing` and place the command file in **app/Controllers**,
-    anyone could access the command with the help of auto-routing via HTTP.
+.. warning:: If you enable :ref:`auto-routing-legacy` and place the command file in **app/Controllers**,
+    anyone could access the command with the help of :ref:`auto-routing-legacy` via HTTP.
 
 Run via CLI
 ===========

user_guide_src/source/incoming/controllers.rst

@@ -313,7 +313,7 @@ your **app/Config/Routes.php** file.
 
 CodeIgniter also permits you to map your URIs using its :ref:`Defined Route Routing <defined-route-routing>`..
 
-.. _controller-auto-routing:
+.. _controller-auto-routing-legacy:
 
 Auto Routing (Legacy)
 *********************

user_guide_src/source/incoming/filters.rst

@@ -71,7 +71,7 @@ This file contains four properties that allow you to configure exactly when the
 
 .. Warning:: It is recommended that you should always add ``*`` at the end of a URI in the filter settings.
     Because a controller method might be accessible by different URLs than you think.
-    For example, when auto-routing is enabled, if you have ``Blog::index``,
+    For example, when :ref:`auto-routing-legacy` is enabled, if you have ``Blog::index``,
     it can be accessible with ``blog``, ``blog/index``, and ``blog/index/1``, etc.
 
 $aliases
@@ -127,8 +127,8 @@ specify the method name in lowercase. It's value would be an array of filters to
 In addition to the standard HTTP methods, this also supports one special case: 'cli'. The 'cli' method would apply to
 all requests that were run from the command line.
 
-.. Warning:: If you use ``$methods`` filters, you should :ref:`disable auto-routing <use-defined-routes-only>`
-    because auto-routing permits any HTTP method to access a controller.
+.. Warning:: If you use ``$methods`` filters, you should :ref:`disable Auto Routing (Legacy) <use-defined-routes-only>`
+    because :ref:`auto-routing-legacy` permits any HTTP method to access a controller.
     Accessing the controller with a method you don't expect could bypass the filter.
 
 $filters

user_guide_src/source/incoming/routing.rst

@@ -361,8 +361,8 @@ available from the command line:
 .. note:: It is recommended to use Spark Commands for CLI scripts instead of calling controllers via CLI.
     See the :doc:`../cli/cli_commands` page for detailed information.
 
-.. warning:: If you enable :ref:`auto-routing` and place the command file in **app/Controllers**,
-    anyone could access the command with the help of auto-routing via HTTP.
+.. warning:: If you enable :ref:`auto-routing-legacy` and place the command file in **app/Controllers**,
+    anyone could access the command with the help of Auto Routing (Legacy) via HTTP.
 
 Global Options
 ==============
@@ -386,8 +386,8 @@ The value for the filter can be a string or an array of strings:
 See :doc:`Controller filters <filters>` for more information on setting up filters.
 
 .. Warning:: If you set filters to routes in **app/Config/Routes.php**
-    (not in **app/Config/Filters.php**), it is recommended to disable auto-routing.
-    When auto-routing is enabled, it may be possible that a controller can be accessed
+    (not in **app/Config/Filters.php**), it is recommended to disable Auto Routing (Legacy).
+    When :ref:`auto-routing-legacy` is enabled, it may be possible that a controller can be accessed
     via a different URL than the configured route,
     in which case the filter you specified to the route will not be applied.
     See :ref:`use-defined-routes-only` to disable auto-routing.
@@ -668,7 +668,7 @@ In this example, if the user were to visit **example.com/products**, and a ``Pro
 .. note:: You cannot access the controller with the URI of the default method name.
     In the example above, you can access **example.com/products**, but if you access **example.com/products/listall**, it will be not found.
 
-.. _auto-routing:
+.. _auto-routing-legacy:
 
 Auto Routing (Legacy)
 *********************
@@ -712,7 +712,7 @@ Consider this URI::
 In the above example, CodeIgniter would attempt to find a controller named **Helloworld.php**
 and executes ``index()`` method with passing ``'1'`` as the first argument.
 
-See :ref:`Auto Routing (Legacy) in Controllers <controller-auto-routing>` for more info.
+See :ref:`Auto Routing (Legacy) in Controllers <controller-auto-routing-legacy>` for more info.
 
 Configuration Options (Legacy)
 ==============================
@@ -732,7 +732,7 @@ The default controller is also used when no matching route has been found, and t
 in the controllers directory. For example, if the user visits **example.com/admin**, if a controller was found at
 **app/Controllers/Admin/Home.php**, it would be used.
 
-See :ref:`Auto Routing in Controllers <controller-auto-routing>` for more info.
+See :ref:`Auto Routing (Legacy) in Controllers <controller-auto-routing-legacy>` for more info.
 
 Default Method (Legacy)
 -----------------------

user_guide_src/source/installation/upgrade_415.rst

@@ -56,8 +56,8 @@ If you want the same behavior as the previous version, set the CSRF filter like
 
 Protecting **GET** method needs only when you use ``form_open()`` auto-generation of CSRF field.
 
-.. Warning:: In general, if you use ``$methods`` filters, you should :ref:`disable auto-routing <use-defined-routes-only>`
-    because auto-routing permits any HTTP method to access a controller.
+.. Warning:: In general, if you use ``$methods`` filters, you should :ref:`disable Auto Routing (Legacy) <use-defined-routes-only>`
+    because :ref:`auto-routing-legacy` permits any HTTP method to access a controller.
     Accessing the controller with a method you don't expect could bypass the filter.
 
 CURLRequest header change

user_guide_src/source/installation/upgrade_4xx.rst

@@ -58,7 +58,7 @@ Application Structure
 Routing
 =======
 
-- The Auto Routing is disabled by default. If you want to use the Auto Routing in the same way as CI3, you need to enable :ref:`auto-routing`.
+- The Auto Routing is disabled by default. If you want to use the Auto Routing in the same way as CI3, you need to enable :ref:`auto-routing-legacy`.
 - CI4 also has an optional new more secure :ref:`auto-routing-improved`.
 
 Model, View and Controller

user_guide_src/source/installation/upgrade_routing.rst

@@ -21,7 +21,7 @@ What has been changed
 Upgrade Guide
 =============
 
-1. If you use the Auto Routing in the same way as CI3, you need to enable :ref:`auto-routing`.
+1. If you use the Auto Routing in the same way as CI3, you need to enable :ref:`auto-routing-legacy`.
 2. The placeholder ``(:any)`` in CI3 will be ``(:segment)`` in CI4.
 3. You have to change the syntax of each routing line and append it in **app/Config/Routes.php**. For example:
 

user_guide_src/source/libraries/security.rst

@@ -147,8 +147,8 @@ It is also possible to enable the CSRF filter only for specific methods:
 
 .. literalinclude:: security/009.php
 
-.. Warning:: If you use ``$methods`` filters, you should :ref:`disable auto-routing <use-defined-routes-only>`
-    because auto-routing permits any HTTP method to access a controller.
+.. Warning:: If you use ``$methods`` filters, you should :ref:`disable Auto Routing (Legacy) <use-defined-routes-only>`
+    because :ref:`auto-routing-legacy` permits any HTTP method to access a controller.
     Accessing the controller with a method you don't expect could bypass the filter.
 
 HTML Forms

user_guide_src/source/libraries/throttler.rst

@@ -73,8 +73,8 @@ Next, we assign it to all POST requests made on the site:
 
 .. literalinclude:: throttler/004.php
 
-.. Warning:: If you use ``$methods`` filters, you should :ref:`disable auto-routing <use-defined-routes-only>`
-    because auto-routing permits any HTTP method to access a controller.
+.. Warning:: If you use ``$methods`` filters, you should :ref:`disable Auto Routing (Legacy) <use-defined-routes-only>`
+    because :ref:`auto-routing-legacy` permits any HTTP method to access a controller.
     Accessing the controller with a method you don't expect could bypass the filter.
 
 And that's all there is to it. Now all POST requests made on the site will have to be rate limited.

user_guide_src/source/tutorial/create_news_items.rst

@@ -22,8 +22,8 @@ Open the **app/Config/Filters.php** file and update the ``$methods`` property li
 It configures the CSRF filter to be enabled for all **POST** requests.
 You can read more about the CSRF protection in :doc:`Security </libraries/security>` library.
 
-.. Warning:: In general, if you use ``$methods`` filters, you should :ref:`disable  Auto Routing (Legacy) <use-defined-routes-only>`
-    because :ref:`auto-routing` permits any HTTP method to access a controller.
+.. Warning:: In general, if you use ``$methods`` filters, you should :ref:`disable Auto Routing (Legacy) <use-defined-routes-only>`
+    because :ref:`auto-routing-legacy` permits any HTTP method to access a controller.
     Accessing the controller with a method you don't expect could bypass the filter.
 
 Create a Form