Merge pull request #5718 from kenjis/fix-docs-cli-only-routes

docs: improve CLI only routing

Author: kenjis

user_guide_src/source/cli/cli.rst

@@ -79,15 +79,18 @@ you with CLI-only tools.
 CLI-Only Routing
 ----------------
 
-In your **Routes.php** file you can create routes that are only accessible from
+In your **app/Config/Routes.php** file you can create routes that are only accessible from
 the CLI as easily as you would create any other route. Instead of using the ``get()``,
 ``post()``, or similar method, you would use the ``cli()`` method. Everything else
 works exactly like a normal route definition:
 
 .. literalinclude:: cli/002.php
    :lines: 2-
 
-For more information, see the :doc:`Routes </incoming/routing>` page.
+For more information, see the :ref:`Routes <command-line-only-routes>` page.
+
+.. warning:: If you don't disable auto-routing and place the command file in **app/Controllers**,
+    anyone could access the command with the help of auto-routing via HTTP.
 
 The CLI Library
 ---------------

user_guide_src/source/incoming/routing.rst

@@ -335,7 +335,9 @@ You can use the ``add()`` method:
     only routes that match the current request method are stored, resulting in fewer routes to scan through
     when trying to find a match.
 
-Command-Line only Routes
+.. _command-line-only-routes:
+
+Command-Line Only Routes
 ========================
 
 You can create routes that work only from the command-line, and are inaccessible from the web browser, with the
@@ -346,6 +348,9 @@ available from the command line:
 .. literalinclude:: routing/028.php
    :lines: 2-
 
+.. warning:: If you don't disable auto-routing and place the command file in **app/Controllers**,
+    anyone could access the command with the help of auto-routing via HTTP.
+
 Global Options
 ==============