Removed spaces and tabs at the end of lines

.clang-format

@@ -19,7 +19,7 @@ AlwaysBreakBeforeMultilineStrings: false
 AlwaysBreakTemplateDeclarations: false
 BinPackArguments: true
 BinPackParameters: true
-BraceWrapping:   
+BraceWrapping:
   AfterClass:      true
   AfterControlStatement: true
   AfterEnum:       true
@@ -54,15 +54,15 @@ DerivePointerAlignment: false
 DisableFormat:   false
 ExperimentalAutoDetectBinPacking: false
 FixNamespaceComments: true
-ForEachMacros:   
+ForEachMacros:
   - forv_Vec
   - for_Vec
   - forp_Vec
   - foreach
   - Q_FOREACH
   - BOOST_FOREACH
 IncludeBlocks:   Preserve
-IncludeCategories: 
+IncludeCategories:
   - Regex:           '^"(llvm|llvm-c|clang|clang-c)/'
     Priority:        2
   - Regex:           '^(<|"(gtest|isl|json)/)'
@@ -92,7 +92,7 @@ PenaltyBreakString: 1000
 PenaltyExcessCharacter: 1000000
 PenaltyReturnTypeOnItsOwnLine: 200
 PointerAlignment: Right
-RawStringFormats: 
+RawStringFormats:
   - Delimiter:       pb
     Language:        TextProto
     BasedOnStyle:    Mozilla

LICENSE

@@ -550,4 +550,4 @@ OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
  * copied and put under another distribution licence
  * [including the GNU Public Licence.]
  */
- 
+

contrib/openssl/README.md

@@ -3,7 +3,7 @@ For the private key operations it spawns a thread to sleep for 5 seconds and the
 
 It should be built as follows.  It must be build against openssl 1.1 or better for access to the ASYNC_*_job apis.
 
-gcc -fPIC -shared -g -o async-test.so -I<path to openssl headers> -L<path to openssl library> -lssl -lcrypto -lpthread async_engine.c 
+gcc -fPIC -shared -g -o async-test.so -I<path to openssl headers> -L<path to openssl library> -lssl -lcrypto -lpthread async_engine.c
 
 load_engine.cnf is an example openssl config file that can be passed to Traffic Server via the proxy.config.ssl.engine_cnf_file setting.
 It describes which crypto engines should be loaded and how they should be used.  In the case of our async-test crypto engine it will be used for

contrib/openssl/async_engine.c

@@ -23,7 +23,7 @@
 
 /*
  * Test engine to exercise the asynchronous job interface
- * It performs the standard RSA operations, but for private key 
+ * It performs the standard RSA operations, but for private key
  * operations spawns a thread to sleep for 5 seconds before resuming
  * the asynchronous job
  */
@@ -236,11 +236,11 @@ spawn_delay_thread()
   } else {
     OSSL_ASYNC_FD pipefds[2] = {0,0};
     OSSL_ASYNC_FD *writefd = OPENSSL_malloc(sizeof(*writefd));
-    pipe(pipefds); 
+    pipe(pipefds);
     signal_fd = *writefd = pipefds[1];
     ASYNC_WAIT_CTX_set_wait_fd(waitctx, engine_id, pipefds[0], writefd, wait_cleanup);
   }
-  
+
   pthread_create(&thread_id, NULL, delay_method, (void *)((intptr_t)signal_fd));
 }
 

doc/admin-guide/plugins/fq_pacing.en.rst

@@ -29,7 +29,7 @@ How it Works
 ------------
 When activated during remap processing, this plugin calls ``setsockopt(SO_MAX_PACING_RATE)`` on the
 client socket. To prevent the rate from leaking to other remap rules the client may access in future
-requests, a hook is set to deactivate the pacing when the current transaction completes. 
+requests, a hook is set to deactivate the pacing when the current transaction completes.
 
 
 Installation

doc/admin-guide/plugins/regex_revalidate.en.rst

@@ -60,7 +60,7 @@ The rule configuration file format is described below in `Revalidation Rules`_.
 
 By default The plugin regularly (every 60 seconds) checks its rules configuration
 file for changes and it will also check for changes when ``traffic_ctl config reload``
-is run. If the file has been modified since its last scan, the contents 
+is run. If the file has been modified since its last scan, the contents
 are read and the in-memory rules list is updated. Thus, new rules may be added and
 existing ones modified without requiring a service restart.
 

doc/admin-guide/plugins/url_sig.en.rst

@@ -245,8 +245,8 @@ Signature
 Signature query parameters embedded in the URL path.
 
     Optionally signature query parameters may be embedded in an opaque base64 encoded container
-    embedded in the URL path.  The format is  a semicolon, siganchor string, base64 encoded 
-    string.  ``url_sig`` automatically detects the use of embedded path parameters. The 
+    embedded in the URL path.  The format is  a semicolon, siganchor string, base64 encoded
+    string.  ``url_sig`` automatically detects the use of embedded path parameters. The
     following example shows how to generate an embedded path parameters with ``sign.pl``::
 
       ./sign.pl --url "http://test-remap.domain.com/vod/t/prog_index.m3u8?appid=2&t=1" --useparts 1 \

doc/admin-guide/plugins/xdebug.en.rst

@@ -58,9 +58,9 @@ Diags
     that :ts:cv:`proxy.config.diags.debug.enabled` is set to ``1``.
 
 log-headers
-    If the ``log-headers`` is requested while :ts:cv:`proxy.config.diags.debug.tags` 
-    is set to ``xdebug.headers`` and :ts:cv:`proxy.config.diags.debug.enabled` is set to ``1``, 
-    then all client and server, request and response headers are logged. 
+    If the ``log-headers`` is requested while :ts:cv:`proxy.config.diags.debug.tags`
+    is set to ``xdebug.headers`` and :ts:cv:`proxy.config.diags.debug.enabled` is set to ``1``,
+    then all client and server, request and response headers are logged.
     Also, the ``X-Debug: log-headers`` header is always added to the upstream request.
 
 X-Cache-Key

doc/appendices/command-line/traffic_cache_tool.en.rst

@@ -85,7 +85,7 @@ Commands
 
 ``clear``
    Clear all the spans by writing updated span headers.
-   
+
    ``span``
      Clears an specific span and it's stripes. The span to be cleared is specified via ``--device``
 
@@ -115,9 +115,9 @@ Commands
    The span to be initialized can be passed via ``--input``
 
 ``find``
-  Determines the stripe in disk cache where the content corresponding to the provided URL may be cached. 
+  Determines the stripe in disk cache where the content corresponding to the provided URL may be cached.
   This command takes an input file which lists all the urls for which the stripe assignment needs to be determined.
-  
+
 ========
 Examples
 ========
@@ -140,27 +140,27 @@ Clear all spans.::
       --volumes=/usr/local/etc/trafficserver/volume.config \
       clear
 
-Clear a single span.:: 
+Clear a single span.::
 
     traffic_cache_tool \
     --span /opt/etc/trafficserver/storage.config \
     --volume /opt/etc/trafficserver/volume.config \
     clear span --device "/dev/sdb3" --write
-    
+
 Initialize a new span.::
- 
+
     traffic_cache_tool \
     --span /opt/etc/trafficserver/storage.config \
     --volume /opt/etc/trafficserver/volume.config \
     init --input "/dev/sdb3" --write
-    
+
 Find Stripe Assignment.::
- 
+
     traffic_cache_tool \
     --span /opt/etc/trafficserver/storage.config \
     --volume /opt/etc/trafficserver/volume.config \
     init --input "/home/user/urls.txt"
-    
+
 ========
 See also
 ========

doc/appendices/command-line/traffic_ctl.en.rst

@@ -261,12 +261,12 @@ traffic_ctl host
 .. option:: down --time seconds --reason 'manual|active|local' HOSTNAME [HOSTNAME ...]
 
     Marks the listed hosts as down so that they will not be chosen as a next hop parent.
-    If the --time option is included, the host is marked down for the specified number of 
-    seconds after which the host will automatically be marked up.  0 seconds marks the host 
+    If the --time option is included, the host is marked down for the specified number of
+    seconds after which the host will automatically be marked up.  0 seconds marks the host
     down indefinitely until marked up manually and is the default. A reason tag may be used
-    when marking a host down.  Valid values are 'manual', 'active', or 'local', 'manual' is 
+    when marking a host down.  Valid values are 'manual', 'active', or 'local', 'manual' is
     used as the default.  The tags are used to indicate wehter the host was marked down
-    manually or by an 'active' or 'local' health check.  There are three reason tag 
+    manually or by an 'active' or 'local' health check.  There are three reason tag
     metrics for each host that may be viewed to see the reason a host was marked down.
 
 .. program:: traffic_ctl host

doc/appendices/command-line/traffic_layout.en.rst

@@ -51,7 +51,7 @@ First we need to create a runroot. It can be created simply by calling command `
 
     traffic_layout init --path /path/to/runroot
 
-A runroot will be created in ``/path/to/runroot``, available for other programs to use. 
+A runroot will be created in ``/path/to/runroot``, available for other programs to use.
 If the path is not specified, the current working directory will be used.
 
 To run traffic_manager, for example, using the runroot, there are several ways:
@@ -71,10 +71,10 @@ Subcommands
 
 init
 ----
-Use the current working directory or the specific path to create runroot. 
+Use the current working directory or the specific path to create runroot.
 The path can be absolute or relative.
 
-workflow: 
+workflow:
     #. Create a sandbox directory for programs to run under.
     #. Copy and symlink build time directories and files to the sandbox, allowing users to modify freely.
     #. Emit a YAML file that defines layout structure for other programs to use (relative path).

doc/developer-guide/api/functions/TSIpStringToAddr.en.rst

@@ -33,10 +33,10 @@ Description
 
 :arg:`str` is expected to be an explicit address, not a hostname.  No hostname resolution is done. This attempts to
 recognize and process a port value if present. It is set appropriately, or to zero if no port was found or it was
-malformed. 
+malformed.
 
 It is intended to deal with the brackets that can optionally surround an IP address (usually IPv6) which in turn are
-used to differentiate between an address and an attached port. E.g. 
+used to differentiate between an address and an attached port. E.g.
 
 .. code-block:: none
 
@@ -45,7 +45,7 @@ used to differentiate between an address and an attached port. E.g.
 Return values
 =============
 
-It returns :data:`TS_SUCCESS` on success, or :data:`TS_ERROR` on failure. 
+It returns :data:`TS_SUCCESS` on success, or :data:`TS_ERROR` on failure.
 
 Notes
 =====

doc/developer-guide/api/functions/TSTypes.en.rst

@@ -43,11 +43,11 @@ more widely. Those are described on this page.
 .. type:: INK_MD5
 
    Buffer type sufficient to contain an MD5 hash value.
-   
+
 .. cpp:class:: INK_MD5
 
    See :type:`INK_MD5`.
-   
+
 .. cpp:class:: RecRawStatBlock
 
    A data block intended to contain |TS| statistics.
@@ -177,11 +177,11 @@ more widely. Those are described on this page.
 .. type:: ModuleVersion
 
     A module version.
-    
+
 .. cpp:type:: ModuleVersion
 
     A module version.
-    
+
 .. cpp:class:: template<typename T> DLL
 
     An anchor for a double linked instrusive list of instance of :arg:`T`.

doc/developer-guide/api/types/TSMgmtTypes.en.rst

@@ -28,63 +28,63 @@ Macros used for RPC communications.
 Management Signals
 ==================
 
-.. c:macro:: MGMT_SIGNAL_PID 
+.. c:macro:: MGMT_SIGNAL_PID
 
-.. c:macro:: MGMT_SIGNAL_MACHINE_UP 
+.. c:macro:: MGMT_SIGNAL_MACHINE_UP
 
-.. c:macro:: MGMT_SIGNAL_MACHINE_DOWN 
+.. c:macro:: MGMT_SIGNAL_MACHINE_DOWN
 
-.. c:macro:: MGMT_SIGNAL_CONFIG_ERROR 
+.. c:macro:: MGMT_SIGNAL_CONFIG_ERROR
 
 .. c:macro:: MGMT_SIGNAL_SYSTEM_ERROR
- 
+
 .. c:macro:: MGMT_SIGNAL_LOG_SPACE_CRISIS
 
-.. c:macro:: MGMT_SIGNAL_CONFIG_FILE_READ 
+.. c:macro:: MGMT_SIGNAL_CONFIG_FILE_READ
 
-.. c:macro:: MGMT_SIGNAL_CACHE_ERROR 
+.. c:macro:: MGMT_SIGNAL_CACHE_ERROR
 
-.. c:macro:: MGMT_SIGNAL_CACHE_WARNING 
+.. c:macro:: MGMT_SIGNAL_CACHE_WARNING
 
-.. c:macro:: MGMT_SIGNAL_LOGGING_ERROR 
+.. c:macro:: MGMT_SIGNAL_LOGGING_ERROR
 
 .. c:macro:: MGMT_SIGNAL_LOGGING_WARNING
 
-.. c:macro:: MGMT_SIGNAL_PLUGIN_SET_CONFIG 
+.. c:macro:: MGMT_SIGNAL_PLUGIN_SET_CONFIG
 
-.. c:macro:: MGMT_SIGNAL_LOG_FILES_ROLLED 
+.. c:macro:: MGMT_SIGNAL_LOG_FILES_ROLLED
 
-.. c:macro:: MGMT_SIGNAL_LIBRECORDS 
+.. c:macro:: MGMT_SIGNAL_LIBRECORDS
 
-.. c:macro:: MGMT_SIGNAL_HTTP_CONGESTED_SERVER 
+.. c:macro:: MGMT_SIGNAL_HTTP_CONGESTED_SERVER
 
-.. c:macro:: MGMT_SIGNAL_HTTP_ALLEVIATED_SERVER 
+.. c:macro:: MGMT_SIGNAL_HTTP_ALLEVIATED_SERVER
 
-.. c:macro:: MGMT_SIGNAL_CONFIG_FILE_CHILD 
+.. c:macro:: MGMT_SIGNAL_CONFIG_FILE_CHILD
 
-.. c:macro:: MGMT_SIGNAL_SAC_SERVER_DOWN 
+.. c:macro:: MGMT_SIGNAL_SAC_SERVER_DOWN
 
 
 Management Events
 ==================
 
 .. c:macro:: MGMT_EVENT_SYNC_KEY
 
-.. c:macro:: MGMT_EVENT_SHUTDOWN 
+.. c:macro:: MGMT_EVENT_SHUTDOWN
 
-.. c:macro:: MGMT_EVENT_RESTART 
+.. c:macro:: MGMT_EVENT_RESTART
 
-.. c:macro:: MGMT_EVENT_BOUNCE 
+.. c:macro:: MGMT_EVENT_BOUNCE
 
-.. c:macro:: MGMT_EVENT_CLEAR_STATS 
+.. c:macro:: MGMT_EVENT_CLEAR_STATS
 
 .. c:macro:: MGMT_EVENT_CONFIG_FILE_UPDATE
 
 .. c:macro:: MGMT_EVENT_PLUGIN_CONFIG_UPDATE
 
 .. c:macro:: MGMT_EVENT_ROLL_LOG_FILES
 
-.. c:macro:: MGMT_EVENT_LIBRECORDS 
+.. c:macro:: MGMT_EVENT_LIBRECORDS
 
 .. c:macro:: MGMT_EVENT_CONFIG_FILE_UPDATE_NO_INC_VERSION
 
@@ -96,7 +96,7 @@ Management Events
 OpTypes (Possible operations or msgs that can be sent between TM and remote clients)
 ====================================================================================
 
-.. cpp:type:: OpType 
+.. cpp:type:: OpType
 
 .. c:macro:: RECORD_SET
 
@@ -138,7 +138,7 @@ OpTypes (Possible operations or msgs that can be sent between TM and remote clie
 
 .. c:macro:: LIFECYCLE_MESSAGE
 
-.. c:macro:: UNDEFINED_OP 
+.. c:macro:: UNDEFINED_OP
 
 
 TSMgmtError

doc/developer-guide/api/types/TSSslSession.en.rst

@@ -38,8 +38,8 @@ Description
 ===========
 
 :type:`TSSslSessionID` represents the SSL session ID as a buffer and length.  The ``TS_SSL_MAX_SSL_SESSION_ID_LENGTH`` is the same value
-as the openssl constant ``SSL_MAX_SSL_SESSION_ID_LENGTH``. The plugin has direct access to this object since creating and 
-manipulating session IDs seems like a fairly common operation (rather than providing an API to access the data via an 
+as the openssl constant ``SSL_MAX_SSL_SESSION_ID_LENGTH``. The plugin has direct access to this object since creating and
+manipulating session IDs seems like a fairly common operation (rather than providing an API to access the data via an
 opaque TS object type).