You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@trafficserver.apache.org by su...@apache.org on 2019/07/16 05:19:25 UTC

[trafficserver] branch master updated (fd5c84a -> 37bf053)

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

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


    from fd5c84a  Convert regression tests for XPACK into Catch based unit tests
     new dd3d500  Update docs to document wipe_field_action that we use in production
     new 37bf053  Fix formatting

The 2 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 doc/admin-guide/files/logging.yaml.en.rst | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)


[trafficserver] 01/02: Update docs to document wipe_field_action that we use in production

Posted by su...@apache.org.
This is an automated email from the ASF dual-hosted git repository.

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

commit dd3d50055c75b5247662ce267c943ed40ceaf796
Author: Sudheer Vinukonda <su...@apache.org>
AuthorDate: Mon Jul 15 15:19:58 2019 -0700

    Update docs to document wipe_field_action that we use in production
---
 doc/admin-guide/files/logging.yaml.en.rst | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/doc/admin-guide/files/logging.yaml.en.rst b/doc/admin-guide/files/logging.yaml.en.rst
index 96a6fe3..a53d053 100644
--- a/doc/admin-guide/files/logging.yaml.en.rst
+++ b/doc/admin-guide/files/logging.yaml.en.rst
@@ -159,14 +159,14 @@ given one.
 Filters
 -------
 
-Two different type of filters are available: ``accept`` and ``reject``.  They
-may be used, optionally, to accept or reject logging for matching events.
+Trafficserver supports different type of filters : ``accept``, ``reject`` and ``wipe_field_value``.
+They may be used, optionally, to accept, reject logging or mask query param values for matching events.
 
 Filter objects are created by assigning them a ``name`` to be used later to
-refer to the filter, as well as an ``action`` (either ``accept`` or
-``reject``). ``Accept`` and ``reject`` filters require a ``condition`` against
-which to match all events. The ``condition`` fields must be in the following
-format::
+refer to the filter, as well as an ``action`` (either ``accept``, ``reject`` or
+``wipe_field_value``). ``Accept``, ``reject`` or ``wipe_field_value` filters require
+a ``condition`` against which to match all events. The ``condition`` fields must
+be in the following format::
 
     <field> <operator> <value>
 


[trafficserver] 02/02: Fix formatting

Posted by su...@apache.org.
This is an automated email from the ASF dual-hosted git repository.

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

commit 37bf05307ed53e4f5cd65601aa67cb5e0d412d16
Author: Sudheer Vinukonda <su...@apache.org>
AuthorDate: Mon Jul 15 15:23:01 2019 -0700

    Fix formatting
---
 doc/admin-guide/files/logging.yaml.en.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/admin-guide/files/logging.yaml.en.rst b/doc/admin-guide/files/logging.yaml.en.rst
index a53d053..f4d6937 100644
--- a/doc/admin-guide/files/logging.yaml.en.rst
+++ b/doc/admin-guide/files/logging.yaml.en.rst
@@ -164,7 +164,7 @@ They may be used, optionally, to accept, reject logging or mask query param valu
 
 Filter objects are created by assigning them a ``name`` to be used later to
 refer to the filter, as well as an ``action`` (either ``accept``, ``reject`` or
-``wipe_field_value``). ``Accept``, ``reject`` or ``wipe_field_value` filters require
+``wipe_field_value``). ``Accept``, ``reject`` or ``wipe_field_value`` filters require
 a ``condition`` against which to match all events. The ``condition`` fields must
 be in the following format::