[trafficserver] branch 8.1.x updated: docs: Add option to mostly strictly check URL characters (#8012) (#8703)

[ez...@apache.org]

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

eze pushed a commit to branch 8.1.x
in repository https://gitbox.apache.org/repos/asf/trafficserver.git


The following commit(s) were added to refs/heads/8.1.x by this push:
     new 8c6f2ed  docs: Add option to mostly strictly check URL characters (#8012) (#8703)
8c6f2ed is described below

commit 8c6f2ed84ba0d8e6255baceb99ee891ebe1ce473
Author: Brian Neradt <br...@gmail.com>
AuthorDate: Tue Mar 15 15:41:50 2022 -0500

    docs: Add option to mostly strictly check URL characters (#8012) (#8703)
    
    (cherry picked from commit 284fe0a0393eca07640f8236f60a6f46f8f132e9)
    
    This just includes the doc changes so that they run via CI separately.
    
    Co-authored-by: Susan Hinrichs <sh...@verizonmedia.com>
---
 doc/admin-guide/files/records.config.en.rst | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/doc/admin-guide/files/records.config.en.rst b/doc/admin-guide/files/records.config.en.rst
index a94e4db..f0db7f8 100644
--- a/doc/admin-guide/files/records.config.en.rst
+++ b/doc/admin-guide/files/records.config.en.rst
@@ -1136,8 +1136,10 @@ mptcp
 
 .. ts:cv:: CONFIG proxy.config.http.strict_uri_parsing INT 0
 
-   Enables (``1``) or disables (``0``) Traffic Server to return a 400 Bad Request
-   if client's request URI includes character which is not RFC 3986 compliant
+   Takes a value between 0 and 2.  ``0`` disables strict_uri_parsing.  Any character can appears
+   in the URI.  ``1`` causes |TS| to return 400 Bad Request
+   if client's request URI includes character which is not RFC 3986 compliant. ``2`` directs |TS|
+   to reject the clients request if it contains whitespace or non-printable characters.
 
 .. ts:cv:: CONFIG proxy.config.http.errors.log_error_pages INT 1
    :reloadable: