[trafficserver] branch master updated: Add docs for parent.config defaults (#8692)

[ro...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

rob pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/trafficserver.git


The following commit(s) were added to refs/heads/master by this push:
     new 6e8af7c  Add docs for parent.config defaults (#8692)
6e8af7c is described below

commit 6e8af7c0cac4c6b7252a9f37528eea631947bfec
Author: Robert O Butts <ro...@users.noreply.github.com>
AuthorDate: Wed Mar 2 11:20:45 2022 -0700

    Add docs for parent.config defaults (#8692)
---
 doc/admin-guide/files/parent.config.en.rst | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/doc/admin-guide/files/parent.config.en.rst b/doc/admin-guide/files/parent.config.en.rst
index 50fa96f..dcb12a0 100644
--- a/doc/admin-guide/files/parent.config.en.rst
+++ b/doc/admin-guide/files/parent.config.en.rst
@@ -222,6 +222,7 @@ The following list shows the possible actions and their allowed values.
       parent is marked down and a new parent is selected to retry the request.  The number of
       retries is controlled by ``max_unavailable_server_retries`` which is set to 1 by default.
     - ``both`` - This enables both ``simple_retry`` and ``unavailable_server_retry`` as described above.
+    - If not set, by default all response codes will be considered a success, and parents will not be retried based on any HTTP response code.
 
     .. Note::
 
@@ -270,7 +271,7 @@ The following list shows the possible actions and their allowed values.
     -  ``strict`` - Traffic Server machines serve requests strictly in
        turn. For example: machine ``proxy1`` serves the first request,
        ``proxy2`` serves the second request, and so on.
-    -  ``false`` - Round robin selection does not occur.
+    -  ``false`` - The default. Round robin selection does not occur.
     -  ``consistent_hash`` - consistent hash of the url so that one parent
        is chosen for a given url. If a parent is down, the traffic that
        would go to the down parent is rehashed amongst the remaining parents.
@@ -290,7 +291,7 @@ The following list shows the possible actions and their allowed values.
 ``go_direct``
     One of the following values:
 
-    -  ``true`` - requests bypass parent hierarchies and go directly to
+    -  ``true`` - The default. Requests bypass parent hierarchies and go directly to
        the origin server.
 
     -  ``false`` - requests do not bypass parent hierarchies.
@@ -300,7 +301,7 @@ The following list shows the possible actions and their allowed values.
 ``qstring``
     One of the following values:
 
-    -  ``consider`` - Use the query string when finding a parent.
+    -  ``consider`` - The default. Use the query string when finding a parent.
 
     -  ``ignore`` - Do not consider the query string when finding a parent. This
        is especially useful when using the ``consistent_hash`` selection strategy,