.. _envoy_v3_api_file_envoy/data/tap/v3/common.proto: Tap common data =============== .. _envoy_v3_api_msg_data.tap.v3.Body: data.tap.v3.Body ---------------- `[data.tap.v3.Body proto] `_ Wrapper for tapped body data. This includes HTTP request/response body, transport socket received and transmitted data, etc. .. code-block:: json { "as_bytes": "...", "as_string": "...", "truncated": "..." } .. _envoy_v3_api_field_data.tap.v3.Body.as_bytes: as_bytes (`bytes `_) Body data as bytes. By default, tap body data will be present in this field, as the proto `bytes` type can contain any valid byte. Only one of :ref:`as_bytes `, :ref:`as_string ` may be set. .. _envoy_v3_api_field_data.tap.v3.Body.as_string: as_string (`string `_) Body data as string. This field is only used when the :ref:`JSON_BODY_AS_STRING ` sink format type is selected. See the documentation for that option for why this is useful. Only one of :ref:`as_bytes `, :ref:`as_string ` may be set. .. _envoy_v3_api_field_data.tap.v3.Body.truncated: truncated (`bool `_) Specifies whether body data has been truncated to fit within the specified :ref:`max_buffered_rx_bytes ` and :ref:`max_buffered_tx_bytes ` settings.