docs: replace auto-routing with "Auto Routing (Legacy)"

Author: kenjis

user_guide_src/source/cli/cli_controllers.rst

@@ -42,7 +42,7 @@ 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-legacy` and place the command file in **app/Controllers**,
-    anyone could access the command with the help of auto-routing via HTTP.
+    anyone could access the command with the help of :ref:`auto-routing-legacy` via HTTP.
 
 Run via CLI
 ===========

user_guide_src/source/incoming/filters.rst

@@ -67,11 +67,11 @@ Configuring Filters
 Once you've created your filters, you need to configure when they get run. This is done in **app/Config/Filters.php**.
 This file contains four properties that allow you to configure exactly when the filters run.
 
-.. Note:: The safest way to apply filters is to :ref:`disable auto-routing <use-defined-routes-only>`, and :ref:`set filters to routes <applying-filters>`.
+.. Note:: The safest way to apply filters is to :ref:`disable Auto Routing (Legacy) <use-defined-routes-only>`, and :ref:`set filters to routes <applying-filters>`.
 
 .. 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

@@ -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.

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/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,7 +22,7 @@ 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>`
+.. 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.