Package io.envoyproxy.envoy.service.ext_proc.v3

Class ProcessingResponse.Builder

java.lang.Object
com.google.protobuf.AbstractMessageLite.Builder
com.google.protobuf.AbstractMessage.Builder<BuilderT>
com.google.protobuf.GeneratedMessageV3.Builder<ProcessingResponse.Builder>
io.envoyproxy.envoy.service.ext_proc.v3.ProcessingResponse.Builder
All Implemented Interfaces:
com.google.protobuf.Message.Builder, com.google.protobuf.MessageLite.Builder, com.google.protobuf.MessageLiteOrBuilder, com.google.protobuf.MessageOrBuilder, ProcessingResponseOrBuilder, Cloneable
Enclosing class:
ProcessingResponse
public static final class ProcessingResponse.Builder extends com.google.protobuf.GeneratedMessageV3.Builder<ProcessingResponse.Builder> implements ProcessingResponseOrBuilder
 This represents the different types of messages the server may send back to the data plane
 when the ``observability_mode`` field in the received ProcessingRequest is set to false.

 * If the corresponding ``BodySendMode`` in the
   :ref:`processing_mode <envoy_v3_api_field_extensions.filters.http.ext_proc.v3.ExternalProcessor.processing_mode>`
   is not set to ``FULL_DUPLEX_STREAMED``, then for every received ProcessingRequest,
   the server must send back exactly one ProcessingResponse message.
 * If it is set to ``FULL_DUPLEX_STREAMED``, the server must follow the API defined
   for this mode to send the ProcessingResponse messages.
 [#next-free-field: 13]
Protobuf type envoy.service.ext_proc.v3.ProcessingResponse

  • Method Details

    • getDescriptor

      public static final com.google.protobuf.Descriptors.Descriptor getDescriptor()

    • internalGetFieldAccessorTable

      protected com.google.protobuf.GeneratedMessageV3.FieldAccessorTable internalGetFieldAccessorTable()
      Specified by:
      internalGetFieldAccessorTable in class com.google.protobuf.GeneratedMessageV3.Builder<ProcessingResponse.Builder>

    • clear

      public ProcessingResponse.Builder clear()
      Specified by:
      clear in interface com.google.protobuf.Message.Builder
      Specified by:
      clear in interface com.google.protobuf.MessageLite.Builder
      Overrides:
      clear in class com.google.protobuf.GeneratedMessageV3.Builder<ProcessingResponse.Builder>

    • getDescriptorForType

      public com.google.protobuf.Descriptors.Descriptor getDescriptorForType()
      Specified by:
      getDescriptorForType in interface com.google.protobuf.Message.Builder
      Specified by:
      getDescriptorForType in interface com.google.protobuf.MessageOrBuilder
      Overrides:
      getDescriptorForType in class com.google.protobuf.GeneratedMessageV3.Builder<ProcessingResponse.Builder>

    • getDefaultInstanceForType

      public ProcessingResponse getDefaultInstanceForType()
      Specified by:
      getDefaultInstanceForType in interface com.google.protobuf.MessageLiteOrBuilder
      Specified by:
      getDefaultInstanceForType in interface com.google.protobuf.MessageOrBuilder

    • build

      public ProcessingResponse build()
      Specified by:
      build in interface com.google.protobuf.Message.Builder
      Specified by:
      build in interface com.google.protobuf.MessageLite.Builder

    • buildPartial

      public ProcessingResponse buildPartial()
      Specified by:
      buildPartial in interface com.google.protobuf.Message.Builder
      Specified by:
      buildPartial in interface com.google.protobuf.MessageLite.Builder

    • clone

      public ProcessingResponse.Builder clone()
      Specified by:
      clone in interface com.google.protobuf.Message.Builder
      Specified by:
      clone in interface com.google.protobuf.MessageLite.Builder
      Overrides:
      clone in class com.google.protobuf.GeneratedMessageV3.Builder<ProcessingResponse.Builder>

    • setField

      public ProcessingResponse.Builder setField(com.google.protobuf.Descriptors.FieldDescriptor field, Object value)
      Specified by:
      setField in interface com.google.protobuf.Message.Builder
      Overrides:
      setField in class com.google.protobuf.GeneratedMessageV3.Builder<ProcessingResponse.Builder>

    • clearField

      public ProcessingResponse.Builder clearField(com.google.protobuf.Descriptors.FieldDescriptor field)
      Specified by:
      clearField in interface com.google.protobuf.Message.Builder
      Overrides:
      clearField in class com.google.protobuf.GeneratedMessageV3.Builder<ProcessingResponse.Builder>

    • clearOneof

      public ProcessingResponse.Builder clearOneof(com.google.protobuf.Descriptors.OneofDescriptor oneof)
      Specified by:
      clearOneof in interface com.google.protobuf.Message.Builder
      Overrides:
      clearOneof in class com.google.protobuf.GeneratedMessageV3.Builder<ProcessingResponse.Builder>

    • setRepeatedField

      public ProcessingResponse.Builder setRepeatedField(com.google.protobuf.Descriptors.FieldDescriptor field, int index, Object value)
      Specified by:
      setRepeatedField in interface com.google.protobuf.Message.Builder
      Overrides:
      setRepeatedField in class com.google.protobuf.GeneratedMessageV3.Builder<ProcessingResponse.Builder>

    • addRepeatedField

      public ProcessingResponse.Builder addRepeatedField(com.google.protobuf.Descriptors.FieldDescriptor field, Object value)
      Specified by:
      addRepeatedField in interface com.google.protobuf.Message.Builder
      Overrides:
      addRepeatedField in class com.google.protobuf.GeneratedMessageV3.Builder<ProcessingResponse.Builder>

    • mergeFrom

      public ProcessingResponse.Builder mergeFrom(com.google.protobuf.Message other)
      Specified by:
      mergeFrom in interface com.google.protobuf.Message.Builder
      Overrides:
      mergeFrom in class com.google.protobuf.AbstractMessage.Builder<ProcessingResponse.Builder>

    • mergeFrom

      public ProcessingResponse.Builder mergeFrom(ProcessingResponse other)

    • isInitialized

      public final boolean isInitialized()
      Specified by:
      isInitialized in interface com.google.protobuf.MessageLiteOrBuilder
      Overrides:
      isInitialized in class com.google.protobuf.GeneratedMessageV3.Builder<ProcessingResponse.Builder>

    • mergeFrom

      public ProcessingResponse.Builder mergeFrom(com.google.protobuf.CodedInputStream input, com.google.protobuf.ExtensionRegistryLite extensionRegistry) throws IOException
      Specified by:
      mergeFrom in interface com.google.protobuf.Message.Builder
      Specified by:
      mergeFrom in interface com.google.protobuf.MessageLite.Builder
      Overrides:
      mergeFrom in class com.google.protobuf.AbstractMessage.Builder<ProcessingResponse.Builder>
      Throws:
      IOException

    • getResponseCase

      public ProcessingResponse.ResponseCase getResponseCase()
      Specified by:
      getResponseCase in interface ProcessingResponseOrBuilder

    • clearResponse

      public ProcessingResponse.Builder clearResponse()

    • hasRequestHeaders

      public boolean hasRequestHeaders()
       The server must send back this message in response to a message with the
 ``request_headers`` field set.
      .envoy.service.ext_proc.v3.HeadersResponse request_headers = 1;
      Specified by:
      hasRequestHeaders in interface ProcessingResponseOrBuilder
      Returns:
      Whether the requestHeaders field is set.

    • getRequestHeaders

      public HeadersResponse getRequestHeaders()
       The server must send back this message in response to a message with the
 ``request_headers`` field set.
      .envoy.service.ext_proc.v3.HeadersResponse request_headers = 1;
      Specified by:
      getRequestHeaders in interface ProcessingResponseOrBuilder
      Returns:
      The requestHeaders.

    • setRequestHeaders

      public ProcessingResponse.Builder setRequestHeaders(HeadersResponse value)
       The server must send back this message in response to a message with the
 ``request_headers`` field set.
      .envoy.service.ext_proc.v3.HeadersResponse request_headers = 1;

    • setRequestHeaders

      public ProcessingResponse.Builder setRequestHeaders(HeadersResponse.Builder builderForValue)
       The server must send back this message in response to a message with the
 ``request_headers`` field set.
      .envoy.service.ext_proc.v3.HeadersResponse request_headers = 1;

    • mergeRequestHeaders

      public ProcessingResponse.Builder mergeRequestHeaders(HeadersResponse value)
       The server must send back this message in response to a message with the
 ``request_headers`` field set.
      .envoy.service.ext_proc.v3.HeadersResponse request_headers = 1;

    • clearRequestHeaders

      public ProcessingResponse.Builder clearRequestHeaders()
       The server must send back this message in response to a message with the
 ``request_headers`` field set.
      .envoy.service.ext_proc.v3.HeadersResponse request_headers = 1;

    • getRequestHeadersBuilder

      public HeadersResponse.Builder getRequestHeadersBuilder()
       The server must send back this message in response to a message with the
 ``request_headers`` field set.
      .envoy.service.ext_proc.v3.HeadersResponse request_headers = 1;

    • getRequestHeadersOrBuilder

      public HeadersResponseOrBuilder getRequestHeadersOrBuilder()
       The server must send back this message in response to a message with the
 ``request_headers`` field set.
      .envoy.service.ext_proc.v3.HeadersResponse request_headers = 1;
      Specified by:
      getRequestHeadersOrBuilder in interface ProcessingResponseOrBuilder

    • hasResponseHeaders

      public boolean hasResponseHeaders()
       The server must send back this message in response to a message with the
 ``response_headers`` field set.
      .envoy.service.ext_proc.v3.HeadersResponse response_headers = 2;
      Specified by:
      hasResponseHeaders in interface ProcessingResponseOrBuilder
      Returns:
      Whether the responseHeaders field is set.

    • getResponseHeaders

      public HeadersResponse getResponseHeaders()
       The server must send back this message in response to a message with the
 ``response_headers`` field set.
      .envoy.service.ext_proc.v3.HeadersResponse response_headers = 2;
      Specified by:
      getResponseHeaders in interface ProcessingResponseOrBuilder
      Returns:
      The responseHeaders.

    • setResponseHeaders

      public ProcessingResponse.Builder setResponseHeaders(HeadersResponse value)
       The server must send back this message in response to a message with the
 ``response_headers`` field set.
      .envoy.service.ext_proc.v3.HeadersResponse response_headers = 2;

    • setResponseHeaders

      public ProcessingResponse.Builder setResponseHeaders(HeadersResponse.Builder builderForValue)
       The server must send back this message in response to a message with the
 ``response_headers`` field set.
      .envoy.service.ext_proc.v3.HeadersResponse response_headers = 2;

    • mergeResponseHeaders

      public ProcessingResponse.Builder mergeResponseHeaders(HeadersResponse value)
       The server must send back this message in response to a message with the
 ``response_headers`` field set.
      .envoy.service.ext_proc.v3.HeadersResponse response_headers = 2;

    • clearResponseHeaders

      public ProcessingResponse.Builder clearResponseHeaders()
       The server must send back this message in response to a message with the
 ``response_headers`` field set.
      .envoy.service.ext_proc.v3.HeadersResponse response_headers = 2;

    • getResponseHeadersBuilder

      public HeadersResponse.Builder getResponseHeadersBuilder()
       The server must send back this message in response to a message with the
 ``response_headers`` field set.
      .envoy.service.ext_proc.v3.HeadersResponse response_headers = 2;

    • getResponseHeadersOrBuilder

      public HeadersResponseOrBuilder getResponseHeadersOrBuilder()
       The server must send back this message in response to a message with the
 ``response_headers`` field set.
      .envoy.service.ext_proc.v3.HeadersResponse response_headers = 2;
      Specified by:
      getResponseHeadersOrBuilder in interface ProcessingResponseOrBuilder

    • hasRequestBody

      public boolean hasRequestBody()
       The server must send back this message in response to a message with
 the ``request_body`` field set.
      .envoy.service.ext_proc.v3.BodyResponse request_body = 3;
      Specified by:
      hasRequestBody in interface ProcessingResponseOrBuilder
      Returns:
      Whether the requestBody field is set.

    • getRequestBody

      public BodyResponse getRequestBody()
       The server must send back this message in response to a message with
 the ``request_body`` field set.
      .envoy.service.ext_proc.v3.BodyResponse request_body = 3;
      Specified by:
      getRequestBody in interface ProcessingResponseOrBuilder
      Returns:
      The requestBody.

    • setRequestBody

      public ProcessingResponse.Builder setRequestBody(BodyResponse value)
       The server must send back this message in response to a message with
 the ``request_body`` field set.
      .envoy.service.ext_proc.v3.BodyResponse request_body = 3;

    • setRequestBody

      public ProcessingResponse.Builder setRequestBody(BodyResponse.Builder builderForValue)
       The server must send back this message in response to a message with
 the ``request_body`` field set.
      .envoy.service.ext_proc.v3.BodyResponse request_body = 3;

    • mergeRequestBody

      public ProcessingResponse.Builder mergeRequestBody(BodyResponse value)
       The server must send back this message in response to a message with
 the ``request_body`` field set.
      .envoy.service.ext_proc.v3.BodyResponse request_body = 3;

    • clearRequestBody

      public ProcessingResponse.Builder clearRequestBody()
       The server must send back this message in response to a message with
 the ``request_body`` field set.
      .envoy.service.ext_proc.v3.BodyResponse request_body = 3;

    • getRequestBodyBuilder

      public BodyResponse.Builder getRequestBodyBuilder()
       The server must send back this message in response to a message with
 the ``request_body`` field set.
      .envoy.service.ext_proc.v3.BodyResponse request_body = 3;

    • getRequestBodyOrBuilder

      public BodyResponseOrBuilder getRequestBodyOrBuilder()
       The server must send back this message in response to a message with
 the ``request_body`` field set.
      .envoy.service.ext_proc.v3.BodyResponse request_body = 3;
      Specified by:
      getRequestBodyOrBuilder in interface ProcessingResponseOrBuilder

    • hasResponseBody

      public boolean hasResponseBody()
       The server must send back this message in response to a message with
 the ``response_body`` field set.
      .envoy.service.ext_proc.v3.BodyResponse response_body = 4;
      Specified by:
      hasResponseBody in interface ProcessingResponseOrBuilder
      Returns:
      Whether the responseBody field is set.

    • getResponseBody

      public BodyResponse getResponseBody()
       The server must send back this message in response to a message with
 the ``response_body`` field set.
      .envoy.service.ext_proc.v3.BodyResponse response_body = 4;
      Specified by:
      getResponseBody in interface ProcessingResponseOrBuilder
      Returns:
      The responseBody.

    • setResponseBody

      public ProcessingResponse.Builder setResponseBody(BodyResponse value)
       The server must send back this message in response to a message with
 the ``response_body`` field set.
      .envoy.service.ext_proc.v3.BodyResponse response_body = 4;

    • setResponseBody

      public ProcessingResponse.Builder setResponseBody(BodyResponse.Builder builderForValue)
       The server must send back this message in response to a message with
 the ``response_body`` field set.
      .envoy.service.ext_proc.v3.BodyResponse response_body = 4;

    • mergeResponseBody

      public ProcessingResponse.Builder mergeResponseBody(BodyResponse value)
       The server must send back this message in response to a message with
 the ``response_body`` field set.
      .envoy.service.ext_proc.v3.BodyResponse response_body = 4;

    • clearResponseBody

      public ProcessingResponse.Builder clearResponseBody()
       The server must send back this message in response to a message with
 the ``response_body`` field set.
      .envoy.service.ext_proc.v3.BodyResponse response_body = 4;

    • getResponseBodyBuilder

      public BodyResponse.Builder getResponseBodyBuilder()
       The server must send back this message in response to a message with
 the ``response_body`` field set.
      .envoy.service.ext_proc.v3.BodyResponse response_body = 4;

    • getResponseBodyOrBuilder

      public BodyResponseOrBuilder getResponseBodyOrBuilder()
       The server must send back this message in response to a message with
 the ``response_body`` field set.
      .envoy.service.ext_proc.v3.BodyResponse response_body = 4;
      Specified by:
      getResponseBodyOrBuilder in interface ProcessingResponseOrBuilder

    • hasRequestTrailers

      public boolean hasRequestTrailers()
       The server must send back this message in response to a message with
 the ``request_trailers`` field set.
      .envoy.service.ext_proc.v3.TrailersResponse request_trailers = 5;
      Specified by:
      hasRequestTrailers in interface ProcessingResponseOrBuilder
      Returns:
      Whether the requestTrailers field is set.

    • getRequestTrailers

      public TrailersResponse getRequestTrailers()
       The server must send back this message in response to a message with
 the ``request_trailers`` field set.
      .envoy.service.ext_proc.v3.TrailersResponse request_trailers = 5;
      Specified by:
      getRequestTrailers in interface ProcessingResponseOrBuilder
      Returns:
      The requestTrailers.

    • setRequestTrailers

      public ProcessingResponse.Builder setRequestTrailers(TrailersResponse value)
       The server must send back this message in response to a message with
 the ``request_trailers`` field set.
      .envoy.service.ext_proc.v3.TrailersResponse request_trailers = 5;

    • setRequestTrailers

      public ProcessingResponse.Builder setRequestTrailers(TrailersResponse.Builder builderForValue)
       The server must send back this message in response to a message with
 the ``request_trailers`` field set.
      .envoy.service.ext_proc.v3.TrailersResponse request_trailers = 5;

    • mergeRequestTrailers

      public ProcessingResponse.Builder mergeRequestTrailers(TrailersResponse value)
       The server must send back this message in response to a message with
 the ``request_trailers`` field set.
      .envoy.service.ext_proc.v3.TrailersResponse request_trailers = 5;

    • clearRequestTrailers

      public ProcessingResponse.Builder clearRequestTrailers()
       The server must send back this message in response to a message with
 the ``request_trailers`` field set.
      .envoy.service.ext_proc.v3.TrailersResponse request_trailers = 5;

    • getRequestTrailersBuilder

      public TrailersResponse.Builder getRequestTrailersBuilder()
       The server must send back this message in response to a message with
 the ``request_trailers`` field set.
      .envoy.service.ext_proc.v3.TrailersResponse request_trailers = 5;

    • getRequestTrailersOrBuilder

      public TrailersResponseOrBuilder getRequestTrailersOrBuilder()
       The server must send back this message in response to a message with
 the ``request_trailers`` field set.
      .envoy.service.ext_proc.v3.TrailersResponse request_trailers = 5;
      Specified by:
      getRequestTrailersOrBuilder in interface ProcessingResponseOrBuilder

    • hasResponseTrailers

      public boolean hasResponseTrailers()
       The server must send back this message in response to a message with
 the ``response_trailers`` field set.
      .envoy.service.ext_proc.v3.TrailersResponse response_trailers = 6;
      Specified by:
      hasResponseTrailers in interface ProcessingResponseOrBuilder
      Returns:
      Whether the responseTrailers field is set.

    • getResponseTrailers

      public TrailersResponse getResponseTrailers()
       The server must send back this message in response to a message with
 the ``response_trailers`` field set.
      .envoy.service.ext_proc.v3.TrailersResponse response_trailers = 6;
      Specified by:
      getResponseTrailers in interface ProcessingResponseOrBuilder
      Returns:
      The responseTrailers.

    • setResponseTrailers

      public ProcessingResponse.Builder setResponseTrailers(TrailersResponse value)
       The server must send back this message in response to a message with
 the ``response_trailers`` field set.
      .envoy.service.ext_proc.v3.TrailersResponse response_trailers = 6;

    • setResponseTrailers

      public ProcessingResponse.Builder setResponseTrailers(TrailersResponse.Builder builderForValue)
       The server must send back this message in response to a message with
 the ``response_trailers`` field set.
      .envoy.service.ext_proc.v3.TrailersResponse response_trailers = 6;

    • mergeResponseTrailers

      public ProcessingResponse.Builder mergeResponseTrailers(TrailersResponse value)
       The server must send back this message in response to a message with
 the ``response_trailers`` field set.
      .envoy.service.ext_proc.v3.TrailersResponse response_trailers = 6;

    • clearResponseTrailers

      public ProcessingResponse.Builder clearResponseTrailers()
       The server must send back this message in response to a message with
 the ``response_trailers`` field set.
      .envoy.service.ext_proc.v3.TrailersResponse response_trailers = 6;

    • getResponseTrailersBuilder

      public TrailersResponse.Builder getResponseTrailersBuilder()
       The server must send back this message in response to a message with
 the ``response_trailers`` field set.
      .envoy.service.ext_proc.v3.TrailersResponse response_trailers = 6;

    • getResponseTrailersOrBuilder

      public TrailersResponseOrBuilder getResponseTrailersOrBuilder()
       The server must send back this message in response to a message with
 the ``response_trailers`` field set.
      .envoy.service.ext_proc.v3.TrailersResponse response_trailers = 6;
      Specified by:
      getResponseTrailersOrBuilder in interface ProcessingResponseOrBuilder

    • hasImmediateResponse

      public boolean hasImmediateResponse()
       If specified, attempt to create a locally generated response, send it
 downstream, and stop processing additional filters and ignore any
 additional messages received from the remote server for this request or
 response. If a response has already started -- for example, if this
 message is sent response to a ``response_body`` message -- then
 this will either ship the reply directly to the downstream codec,
 or reset the stream.
      .envoy.service.ext_proc.v3.ImmediateResponse immediate_response = 7;
      Specified by:
      hasImmediateResponse in interface ProcessingResponseOrBuilder
      Returns:
      Whether the immediateResponse field is set.

    • getImmediateResponse

      public ImmediateResponse getImmediateResponse()
       If specified, attempt to create a locally generated response, send it
 downstream, and stop processing additional filters and ignore any
 additional messages received from the remote server for this request or
 response. If a response has already started -- for example, if this
 message is sent response to a ``response_body`` message -- then
 this will either ship the reply directly to the downstream codec,
 or reset the stream.
      .envoy.service.ext_proc.v3.ImmediateResponse immediate_response = 7;
      Specified by:
      getImmediateResponse in interface ProcessingResponseOrBuilder
      Returns:
      The immediateResponse.

    • setImmediateResponse

      public ProcessingResponse.Builder setImmediateResponse(ImmediateResponse value)
       If specified, attempt to create a locally generated response, send it
 downstream, and stop processing additional filters and ignore any
 additional messages received from the remote server for this request or
 response. If a response has already started -- for example, if this
 message is sent response to a ``response_body`` message -- then
 this will either ship the reply directly to the downstream codec,
 or reset the stream.
      .envoy.service.ext_proc.v3.ImmediateResponse immediate_response = 7;

    • setImmediateResponse

      public ProcessingResponse.Builder setImmediateResponse(ImmediateResponse.Builder builderForValue)
       If specified, attempt to create a locally generated response, send it
 downstream, and stop processing additional filters and ignore any
 additional messages received from the remote server for this request or
 response. If a response has already started -- for example, if this
 message is sent response to a ``response_body`` message -- then
 this will either ship the reply directly to the downstream codec,
 or reset the stream.
      .envoy.service.ext_proc.v3.ImmediateResponse immediate_response = 7;

    • mergeImmediateResponse

      public ProcessingResponse.Builder mergeImmediateResponse(ImmediateResponse value)
       If specified, attempt to create a locally generated response, send it
 downstream, and stop processing additional filters and ignore any
 additional messages received from the remote server for this request or
 response. If a response has already started -- for example, if this
 message is sent response to a ``response_body`` message -- then
 this will either ship the reply directly to the downstream codec,
 or reset the stream.
      .envoy.service.ext_proc.v3.ImmediateResponse immediate_response = 7;

    • clearImmediateResponse

      public ProcessingResponse.Builder clearImmediateResponse()
       If specified, attempt to create a locally generated response, send it
 downstream, and stop processing additional filters and ignore any
 additional messages received from the remote server for this request or
 response. If a response has already started -- for example, if this
 message is sent response to a ``response_body`` message -- then
 this will either ship the reply directly to the downstream codec,
 or reset the stream.
      .envoy.service.ext_proc.v3.ImmediateResponse immediate_response = 7;

    • getImmediateResponseBuilder

      public ImmediateResponse.Builder getImmediateResponseBuilder()
       If specified, attempt to create a locally generated response, send it
 downstream, and stop processing additional filters and ignore any
 additional messages received from the remote server for this request or
 response. If a response has already started -- for example, if this
 message is sent response to a ``response_body`` message -- then
 this will either ship the reply directly to the downstream codec,
 or reset the stream.
      .envoy.service.ext_proc.v3.ImmediateResponse immediate_response = 7;

    • getImmediateResponseOrBuilder

      public ImmediateResponseOrBuilder getImmediateResponseOrBuilder()
       If specified, attempt to create a locally generated response, send it
 downstream, and stop processing additional filters and ignore any
 additional messages received from the remote server for this request or
 response. If a response has already started -- for example, if this
 message is sent response to a ``response_body`` message -- then
 this will either ship the reply directly to the downstream codec,
 or reset the stream.
      .envoy.service.ext_proc.v3.ImmediateResponse immediate_response = 7;
      Specified by:
      getImmediateResponseOrBuilder in interface ProcessingResponseOrBuilder

    • hasStreamedImmediateResponse

      public boolean hasStreamedImmediateResponse()
       The server sends back this message to initiate or continue local response streaming.
 The server must initiate local response streaming with the ``headers_response`` in response to a ProcessingRequest
 with the ``request_headers`` only.
 The server may follow up with multiple messages containing ``body_response``. The server must indicate
 end of stream by setting ``end_of_stream`` to ``true`` in the ``headers_response``
 or ``body_response`` message or by sending a ``trailers_response`` message.
 The client may send a ``request_body`` or ``request_trailers`` to the server depending on configuration.
 The streaming local response can only be sent when the ``request_header_mode`` in the filter
 :ref:`processing_mode <envoy_v3_api_field_extensions.filters.http.ext_proc.v3.ExternalProcessor.processing_mode>`
 is set to ``SEND``. The ext_proc server should not send StreamedImmediateResponse if it did not observe request headers,
 as it will result in the race with the upstream server response and reset of the client request.
 Presently only the FULL_DUPLEX_STREAMED or NONE body modes are supported.
      .envoy.service.ext_proc.v3.StreamedImmediateResponse streamed_immediate_response = 11;
      Specified by:
      hasStreamedImmediateResponse in interface ProcessingResponseOrBuilder
      Returns:
      Whether the streamedImmediateResponse field is set.

    • getStreamedImmediateResponse

      public StreamedImmediateResponse getStreamedImmediateResponse()
       The server sends back this message to initiate or continue local response streaming.
 The server must initiate local response streaming with the ``headers_response`` in response to a ProcessingRequest
 with the ``request_headers`` only.
 The server may follow up with multiple messages containing ``body_response``. The server must indicate
 end of stream by setting ``end_of_stream`` to ``true`` in the ``headers_response``
 or ``body_response`` message or by sending a ``trailers_response`` message.
 The client may send a ``request_body`` or ``request_trailers`` to the server depending on configuration.
 The streaming local response can only be sent when the ``request_header_mode`` in the filter
 :ref:`processing_mode <envoy_v3_api_field_extensions.filters.http.ext_proc.v3.ExternalProcessor.processing_mode>`
 is set to ``SEND``. The ext_proc server should not send StreamedImmediateResponse if it did not observe request headers,
 as it will result in the race with the upstream server response and reset of the client request.
 Presently only the FULL_DUPLEX_STREAMED or NONE body modes are supported.
      .envoy.service.ext_proc.v3.StreamedImmediateResponse streamed_immediate_response = 11;
      Specified by:
      getStreamedImmediateResponse in interface ProcessingResponseOrBuilder
      Returns:
      The streamedImmediateResponse.

    • setStreamedImmediateResponse

      public ProcessingResponse.Builder setStreamedImmediateResponse(StreamedImmediateResponse value)
       The server sends back this message to initiate or continue local response streaming.
 The server must initiate local response streaming with the ``headers_response`` in response to a ProcessingRequest
 with the ``request_headers`` only.
 The server may follow up with multiple messages containing ``body_response``. The server must indicate
 end of stream by setting ``end_of_stream`` to ``true`` in the ``headers_response``
 or ``body_response`` message or by sending a ``trailers_response`` message.
 The client may send a ``request_body`` or ``request_trailers`` to the server depending on configuration.
 The streaming local response can only be sent when the ``request_header_mode`` in the filter
 :ref:`processing_mode <envoy_v3_api_field_extensions.filters.http.ext_proc.v3.ExternalProcessor.processing_mode>`
 is set to ``SEND``. The ext_proc server should not send StreamedImmediateResponse if it did not observe request headers,
 as it will result in the race with the upstream server response and reset of the client request.
 Presently only the FULL_DUPLEX_STREAMED or NONE body modes are supported.
      .envoy.service.ext_proc.v3.StreamedImmediateResponse streamed_immediate_response = 11;

    • setStreamedImmediateResponse

      public ProcessingResponse.Builder setStreamedImmediateResponse(StreamedImmediateResponse.Builder builderForValue)
       The server sends back this message to initiate or continue local response streaming.
 The server must initiate local response streaming with the ``headers_response`` in response to a ProcessingRequest
 with the ``request_headers`` only.
 The server may follow up with multiple messages containing ``body_response``. The server must indicate
 end of stream by setting ``end_of_stream`` to ``true`` in the ``headers_response``
 or ``body_response`` message or by sending a ``trailers_response`` message.
 The client may send a ``request_body`` or ``request_trailers`` to the server depending on configuration.
 The streaming local response can only be sent when the ``request_header_mode`` in the filter
 :ref:`processing_mode <envoy_v3_api_field_extensions.filters.http.ext_proc.v3.ExternalProcessor.processing_mode>`
 is set to ``SEND``. The ext_proc server should not send StreamedImmediateResponse if it did not observe request headers,
 as it will result in the race with the upstream server response and reset of the client request.
 Presently only the FULL_DUPLEX_STREAMED or NONE body modes are supported.
      .envoy.service.ext_proc.v3.StreamedImmediateResponse streamed_immediate_response = 11;

    • mergeStreamedImmediateResponse

      public ProcessingResponse.Builder mergeStreamedImmediateResponse(StreamedImmediateResponse value)
       The server sends back this message to initiate or continue local response streaming.
 The server must initiate local response streaming with the ``headers_response`` in response to a ProcessingRequest
 with the ``request_headers`` only.
 The server may follow up with multiple messages containing ``body_response``. The server must indicate
 end of stream by setting ``end_of_stream`` to ``true`` in the ``headers_response``
 or ``body_response`` message or by sending a ``trailers_response`` message.
 The client may send a ``request_body`` or ``request_trailers`` to the server depending on configuration.
 The streaming local response can only be sent when the ``request_header_mode`` in the filter
 :ref:`processing_mode <envoy_v3_api_field_extensions.filters.http.ext_proc.v3.ExternalProcessor.processing_mode>`
 is set to ``SEND``. The ext_proc server should not send StreamedImmediateResponse if it did not observe request headers,
 as it will result in the race with the upstream server response and reset of the client request.
 Presently only the FULL_DUPLEX_STREAMED or NONE body modes are supported.
      .envoy.service.ext_proc.v3.StreamedImmediateResponse streamed_immediate_response = 11;

    • clearStreamedImmediateResponse

      public ProcessingResponse.Builder clearStreamedImmediateResponse()
       The server sends back this message to initiate or continue local response streaming.
 The server must initiate local response streaming with the ``headers_response`` in response to a ProcessingRequest
 with the ``request_headers`` only.
 The server may follow up with multiple messages containing ``body_response``. The server must indicate
 end of stream by setting ``end_of_stream`` to ``true`` in the ``headers_response``
 or ``body_response`` message or by sending a ``trailers_response`` message.
 The client may send a ``request_body`` or ``request_trailers`` to the server depending on configuration.
 The streaming local response can only be sent when the ``request_header_mode`` in the filter
 :ref:`processing_mode <envoy_v3_api_field_extensions.filters.http.ext_proc.v3.ExternalProcessor.processing_mode>`
 is set to ``SEND``. The ext_proc server should not send StreamedImmediateResponse if it did not observe request headers,
 as it will result in the race with the upstream server response and reset of the client request.
 Presently only the FULL_DUPLEX_STREAMED or NONE body modes are supported.
      .envoy.service.ext_proc.v3.StreamedImmediateResponse streamed_immediate_response = 11;

    • getStreamedImmediateResponseBuilder

      public StreamedImmediateResponse.Builder getStreamedImmediateResponseBuilder()
       The server sends back this message to initiate or continue local response streaming.
 The server must initiate local response streaming with the ``headers_response`` in response to a ProcessingRequest
 with the ``request_headers`` only.
 The server may follow up with multiple messages containing ``body_response``. The server must indicate
 end of stream by setting ``end_of_stream`` to ``true`` in the ``headers_response``
 or ``body_response`` message or by sending a ``trailers_response`` message.
 The client may send a ``request_body`` or ``request_trailers`` to the server depending on configuration.
 The streaming local response can only be sent when the ``request_header_mode`` in the filter
 :ref:`processing_mode <envoy_v3_api_field_extensions.filters.http.ext_proc.v3.ExternalProcessor.processing_mode>`
 is set to ``SEND``. The ext_proc server should not send StreamedImmediateResponse if it did not observe request headers,
 as it will result in the race with the upstream server response and reset of the client request.
 Presently only the FULL_DUPLEX_STREAMED or NONE body modes are supported.
      .envoy.service.ext_proc.v3.StreamedImmediateResponse streamed_immediate_response = 11;

    • getStreamedImmediateResponseOrBuilder

      public StreamedImmediateResponseOrBuilder getStreamedImmediateResponseOrBuilder()
       The server sends back this message to initiate or continue local response streaming.
 The server must initiate local response streaming with the ``headers_response`` in response to a ProcessingRequest
 with the ``request_headers`` only.
 The server may follow up with multiple messages containing ``body_response``. The server must indicate
 end of stream by setting ``end_of_stream`` to ``true`` in the ``headers_response``
 or ``body_response`` message or by sending a ``trailers_response`` message.
 The client may send a ``request_body`` or ``request_trailers`` to the server depending on configuration.
 The streaming local response can only be sent when the ``request_header_mode`` in the filter
 :ref:`processing_mode <envoy_v3_api_field_extensions.filters.http.ext_proc.v3.ExternalProcessor.processing_mode>`
 is set to ``SEND``. The ext_proc server should not send StreamedImmediateResponse if it did not observe request headers,
 as it will result in the race with the upstream server response and reset of the client request.
 Presently only the FULL_DUPLEX_STREAMED or NONE body modes are supported.
      .envoy.service.ext_proc.v3.StreamedImmediateResponse streamed_immediate_response = 11;
      Specified by:
      getStreamedImmediateResponseOrBuilder in interface ProcessingResponseOrBuilder

    • hasDynamicMetadata

      public boolean hasDynamicMetadata()
       Optional metadata that will be emitted as dynamic metadata to be consumed by
 following filters. This metadata will be placed in the namespace(s) specified by the top-level
 field name(s) of the struct.
      .google.protobuf.Struct dynamic_metadata = 8;
      Specified by:
      hasDynamicMetadata in interface ProcessingResponseOrBuilder
      Returns:
      Whether the dynamicMetadata field is set.

    • getDynamicMetadata

      public com.google.protobuf.Struct getDynamicMetadata()
       Optional metadata that will be emitted as dynamic metadata to be consumed by
 following filters. This metadata will be placed in the namespace(s) specified by the top-level
 field name(s) of the struct.
      .google.protobuf.Struct dynamic_metadata = 8;
      Specified by:
      getDynamicMetadata in interface ProcessingResponseOrBuilder
      Returns:
      The dynamicMetadata.

    • setDynamicMetadata

      public ProcessingResponse.Builder setDynamicMetadata(com.google.protobuf.Struct value)
       Optional metadata that will be emitted as dynamic metadata to be consumed by
 following filters. This metadata will be placed in the namespace(s) specified by the top-level
 field name(s) of the struct.
      .google.protobuf.Struct dynamic_metadata = 8;

    • setDynamicMetadata

      public ProcessingResponse.Builder setDynamicMetadata(com.google.protobuf.Struct.Builder builderForValue)
       Optional metadata that will be emitted as dynamic metadata to be consumed by
 following filters. This metadata will be placed in the namespace(s) specified by the top-level
 field name(s) of the struct.
      .google.protobuf.Struct dynamic_metadata = 8;

    • mergeDynamicMetadata

      public ProcessingResponse.Builder mergeDynamicMetadata(com.google.protobuf.Struct value)
       Optional metadata that will be emitted as dynamic metadata to be consumed by
 following filters. This metadata will be placed in the namespace(s) specified by the top-level
 field name(s) of the struct.
      .google.protobuf.Struct dynamic_metadata = 8;

    • clearDynamicMetadata

      public ProcessingResponse.Builder clearDynamicMetadata()
       Optional metadata that will be emitted as dynamic metadata to be consumed by
 following filters. This metadata will be placed in the namespace(s) specified by the top-level
 field name(s) of the struct.
      .google.protobuf.Struct dynamic_metadata = 8;

    • getDynamicMetadataBuilder

      public com.google.protobuf.Struct.Builder getDynamicMetadataBuilder()
       Optional metadata that will be emitted as dynamic metadata to be consumed by
 following filters. This metadata will be placed in the namespace(s) specified by the top-level
 field name(s) of the struct.
      .google.protobuf.Struct dynamic_metadata = 8;

    • getDynamicMetadataOrBuilder

      public com.google.protobuf.StructOrBuilder getDynamicMetadataOrBuilder()
       Optional metadata that will be emitted as dynamic metadata to be consumed by
 following filters. This metadata will be placed in the namespace(s) specified by the top-level
 field name(s) of the struct.
      .google.protobuf.Struct dynamic_metadata = 8;
      Specified by:
      getDynamicMetadataOrBuilder in interface ProcessingResponseOrBuilder

    • hasModeOverride

      public boolean hasModeOverride()
       Override how parts of the HTTP request and response are processed
 for the duration of this particular request/response only. Servers
 may use this to intelligently control how requests are processed
 based on the headers and other metadata that they see.
 This field is only applicable when servers responding to the header requests.
 If it is set in the response to the body or trailer requests, it will be ignored by the data plane.
 It is also ignored by the data plane when the ext_proc filter config
 :ref:`allow_mode_override
 <envoy_v3_api_field_extensions.filters.http.ext_proc.v3.ExternalProcessor.allow_mode_override>`
 is set to false, or
 :ref:`send_body_without_waiting_for_header_response
 <envoy_v3_api_field_extensions.filters.http.ext_proc.v3.ExternalProcessor.send_body_without_waiting_for_header_response>`
 is set to true.
      .envoy.extensions.filters.http.ext_proc.v3.ProcessingMode mode_override = 9;
      Specified by:
      hasModeOverride in interface ProcessingResponseOrBuilder
      Returns:
      Whether the modeOverride field is set.

    • getModeOverride

      public ProcessingMode getModeOverride()
       Override how parts of the HTTP request and response are processed
 for the duration of this particular request/response only. Servers
 may use this to intelligently control how requests are processed
 based on the headers and other metadata that they see.
 This field is only applicable when servers responding to the header requests.
 If it is set in the response to the body or trailer requests, it will be ignored by the data plane.
 It is also ignored by the data plane when the ext_proc filter config
 :ref:`allow_mode_override
 <envoy_v3_api_field_extensions.filters.http.ext_proc.v3.ExternalProcessor.allow_mode_override>`
 is set to false, or
 :ref:`send_body_without_waiting_for_header_response
 <envoy_v3_api_field_extensions.filters.http.ext_proc.v3.ExternalProcessor.send_body_without_waiting_for_header_response>`
 is set to true.
      .envoy.extensions.filters.http.ext_proc.v3.ProcessingMode mode_override = 9;
      Specified by:
      getModeOverride in interface ProcessingResponseOrBuilder
      Returns:
      The modeOverride.

    • setModeOverride

      public ProcessingResponse.Builder setModeOverride(ProcessingMode value)
       Override how parts of the HTTP request and response are processed
 for the duration of this particular request/response only. Servers
 may use this to intelligently control how requests are processed
 based on the headers and other metadata that they see.
 This field is only applicable when servers responding to the header requests.
 If it is set in the response to the body or trailer requests, it will be ignored by the data plane.
 It is also ignored by the data plane when the ext_proc filter config
 :ref:`allow_mode_override
 <envoy_v3_api_field_extensions.filters.http.ext_proc.v3.ExternalProcessor.allow_mode_override>`
 is set to false, or
 :ref:`send_body_without_waiting_for_header_response
 <envoy_v3_api_field_extensions.filters.http.ext_proc.v3.ExternalProcessor.send_body_without_waiting_for_header_response>`
 is set to true.
      .envoy.extensions.filters.http.ext_proc.v3.ProcessingMode mode_override = 9;

    • setModeOverride

      public ProcessingResponse.Builder setModeOverride(ProcessingMode.Builder builderForValue)
       Override how parts of the HTTP request and response are processed
 for the duration of this particular request/response only. Servers
 may use this to intelligently control how requests are processed
 based on the headers and other metadata that they see.
 This field is only applicable when servers responding to the header requests.
 If it is set in the response to the body or trailer requests, it will be ignored by the data plane.
 It is also ignored by the data plane when the ext_proc filter config
 :ref:`allow_mode_override
 <envoy_v3_api_field_extensions.filters.http.ext_proc.v3.ExternalProcessor.allow_mode_override>`
 is set to false, or
 :ref:`send_body_without_waiting_for_header_response
 <envoy_v3_api_field_extensions.filters.http.ext_proc.v3.ExternalProcessor.send_body_without_waiting_for_header_response>`
 is set to true.
      .envoy.extensions.filters.http.ext_proc.v3.ProcessingMode mode_override = 9;

    • mergeModeOverride

      public ProcessingResponse.Builder mergeModeOverride(ProcessingMode value)
       Override how parts of the HTTP request and response are processed
 for the duration of this particular request/response only. Servers
 may use this to intelligently control how requests are processed
 based on the headers and other metadata that they see.
 This field is only applicable when servers responding to the header requests.
 If it is set in the response to the body or trailer requests, it will be ignored by the data plane.
 It is also ignored by the data plane when the ext_proc filter config
 :ref:`allow_mode_override
 <envoy_v3_api_field_extensions.filters.http.ext_proc.v3.ExternalProcessor.allow_mode_override>`
 is set to false, or
 :ref:`send_body_without_waiting_for_header_response
 <envoy_v3_api_field_extensions.filters.http.ext_proc.v3.ExternalProcessor.send_body_without_waiting_for_header_response>`
 is set to true.
      .envoy.extensions.filters.http.ext_proc.v3.ProcessingMode mode_override = 9;

    • clearModeOverride

      public ProcessingResponse.Builder clearModeOverride()
       Override how parts of the HTTP request and response are processed
 for the duration of this particular request/response only. Servers
 may use this to intelligently control how requests are processed
 based on the headers and other metadata that they see.
 This field is only applicable when servers responding to the header requests.
 If it is set in the response to the body or trailer requests, it will be ignored by the data plane.
 It is also ignored by the data plane when the ext_proc filter config
 :ref:`allow_mode_override
 <envoy_v3_api_field_extensions.filters.http.ext_proc.v3.ExternalProcessor.allow_mode_override>`
 is set to false, or
 :ref:`send_body_without_waiting_for_header_response
 <envoy_v3_api_field_extensions.filters.http.ext_proc.v3.ExternalProcessor.send_body_without_waiting_for_header_response>`
 is set to true.
      .envoy.extensions.filters.http.ext_proc.v3.ProcessingMode mode_override = 9;

    • getModeOverrideBuilder

      public ProcessingMode.Builder getModeOverrideBuilder()
       Override how parts of the HTTP request and response are processed
 for the duration of this particular request/response only. Servers
 may use this to intelligently control how requests are processed
 based on the headers and other metadata that they see.
 This field is only applicable when servers responding to the header requests.
 If it is set in the response to the body or trailer requests, it will be ignored by the data plane.
 It is also ignored by the data plane when the ext_proc filter config
 :ref:`allow_mode_override
 <envoy_v3_api_field_extensions.filters.http.ext_proc.v3.ExternalProcessor.allow_mode_override>`
 is set to false, or
 :ref:`send_body_without_waiting_for_header_response
 <envoy_v3_api_field_extensions.filters.http.ext_proc.v3.ExternalProcessor.send_body_without_waiting_for_header_response>`
 is set to true.
      .envoy.extensions.filters.http.ext_proc.v3.ProcessingMode mode_override = 9;

    • getModeOverrideOrBuilder

      public ProcessingModeOrBuilder getModeOverrideOrBuilder()
       Override how parts of the HTTP request and response are processed
 for the duration of this particular request/response only. Servers
 may use this to intelligently control how requests are processed
 based on the headers and other metadata that they see.
 This field is only applicable when servers responding to the header requests.
 If it is set in the response to the body or trailer requests, it will be ignored by the data plane.
 It is also ignored by the data plane when the ext_proc filter config
 :ref:`allow_mode_override
 <envoy_v3_api_field_extensions.filters.http.ext_proc.v3.ExternalProcessor.allow_mode_override>`
 is set to false, or
 :ref:`send_body_without_waiting_for_header_response
 <envoy_v3_api_field_extensions.filters.http.ext_proc.v3.ExternalProcessor.send_body_without_waiting_for_header_response>`
 is set to true.
      .envoy.extensions.filters.http.ext_proc.v3.ProcessingMode mode_override = 9;
      Specified by:
      getModeOverrideOrBuilder in interface ProcessingResponseOrBuilder

    • getRequestDrain

      public boolean getRequestDrain()
       [#not-implemented-hide:]
 Used only in ``FULL_DUPLEX_STREAMED`` and ``GRPC`` body send modes.
 Instructs the data plane to stop sending body data and to send a
 half-close on the ext_proc stream. The ext_proc server should then echo
 back all subsequent body contents as-is until it sees the client's
 half-close, at which point the ext_proc server can terminate the stream
 with an OK status. This provides a safe way for the ext_proc server
 to indicate that it does not need to see the rest of the stream;
 without this, the ext_proc server could not terminate the stream
 early, because it would wind up dropping any body contents that the
 client had already sent before it saw the ext_proc stream termination.
      bool request_drain = 12;
      Specified by:
      getRequestDrain in interface ProcessingResponseOrBuilder
      Returns:
      The requestDrain.

    • setRequestDrain

      public ProcessingResponse.Builder setRequestDrain(boolean value)
       [#not-implemented-hide:]
 Used only in ``FULL_DUPLEX_STREAMED`` and ``GRPC`` body send modes.
 Instructs the data plane to stop sending body data and to send a
 half-close on the ext_proc stream. The ext_proc server should then echo
 back all subsequent body contents as-is until it sees the client's
 half-close, at which point the ext_proc server can terminate the stream
 with an OK status. This provides a safe way for the ext_proc server
 to indicate that it does not need to see the rest of the stream;
 without this, the ext_proc server could not terminate the stream
 early, because it would wind up dropping any body contents that the
 client had already sent before it saw the ext_proc stream termination.
      bool request_drain = 12;
      Parameters:
      value - The requestDrain to set.
      Returns:
      This builder for chaining.

    • clearRequestDrain

      public ProcessingResponse.Builder clearRequestDrain()
       [#not-implemented-hide:]
 Used only in ``FULL_DUPLEX_STREAMED`` and ``GRPC`` body send modes.
 Instructs the data plane to stop sending body data and to send a
 half-close on the ext_proc stream. The ext_proc server should then echo
 back all subsequent body contents as-is until it sees the client's
 half-close, at which point the ext_proc server can terminate the stream
 with an OK status. This provides a safe way for the ext_proc server
 to indicate that it does not need to see the rest of the stream;
 without this, the ext_proc server could not terminate the stream
 early, because it would wind up dropping any body contents that the
 client had already sent before it saw the ext_proc stream termination.
      bool request_drain = 12;
      Returns:
      This builder for chaining.

    • hasOverrideMessageTimeout

      public boolean hasOverrideMessageTimeout()
       When ext_proc server receives a request message, in case it needs more
 time to process the message, it sends back a ProcessingResponse message
 with a new timeout value. When the data plane receives this response
 message, it ignores other fields in the response, just stop the original
 timer, which has the timeout value specified in
 :ref:`message_timeout
 <envoy_v3_api_field_extensions.filters.http.ext_proc.v3.ExternalProcessor.message_timeout>`
 and start a new timer with this ``override_message_timeout`` value and keep the
 data plane ext_proc filter state machine intact.
 Has to be >= 1ms and <=
 :ref:`max_message_timeout <envoy_v3_api_field_extensions.filters.http.ext_proc.v3.ExternalProcessor.max_message_timeout>`
 Such message can be sent at most once in a particular data plane ext_proc filter processing state.
 To enable this API, one has to set ``max_message_timeout`` to a number >= 1ms.
      .google.protobuf.Duration override_message_timeout = 10;
      Specified by:
      hasOverrideMessageTimeout in interface ProcessingResponseOrBuilder
      Returns:
      Whether the overrideMessageTimeout field is set.

    • getOverrideMessageTimeout

      public com.google.protobuf.Duration getOverrideMessageTimeout()
       When ext_proc server receives a request message, in case it needs more
 time to process the message, it sends back a ProcessingResponse message
 with a new timeout value. When the data plane receives this response
 message, it ignores other fields in the response, just stop the original
 timer, which has the timeout value specified in
 :ref:`message_timeout
 <envoy_v3_api_field_extensions.filters.http.ext_proc.v3.ExternalProcessor.message_timeout>`
 and start a new timer with this ``override_message_timeout`` value and keep the
 data plane ext_proc filter state machine intact.
 Has to be >= 1ms and <=
 :ref:`max_message_timeout <envoy_v3_api_field_extensions.filters.http.ext_proc.v3.ExternalProcessor.max_message_timeout>`
 Such message can be sent at most once in a particular data plane ext_proc filter processing state.
 To enable this API, one has to set ``max_message_timeout`` to a number >= 1ms.
      .google.protobuf.Duration override_message_timeout = 10;
      Specified by:
      getOverrideMessageTimeout in interface ProcessingResponseOrBuilder
      Returns:
      The overrideMessageTimeout.

    • setOverrideMessageTimeout

      public ProcessingResponse.Builder setOverrideMessageTimeout(com.google.protobuf.Duration value)
       When ext_proc server receives a request message, in case it needs more
 time to process the message, it sends back a ProcessingResponse message
 with a new timeout value. When the data plane receives this response
 message, it ignores other fields in the response, just stop the original
 timer, which has the timeout value specified in
 :ref:`message_timeout
 <envoy_v3_api_field_extensions.filters.http.ext_proc.v3.ExternalProcessor.message_timeout>`
 and start a new timer with this ``override_message_timeout`` value and keep the
 data plane ext_proc filter state machine intact.
 Has to be >= 1ms and <=
 :ref:`max_message_timeout <envoy_v3_api_field_extensions.filters.http.ext_proc.v3.ExternalProcessor.max_message_timeout>`
 Such message can be sent at most once in a particular data plane ext_proc filter processing state.
 To enable this API, one has to set ``max_message_timeout`` to a number >= 1ms.
      .google.protobuf.Duration override_message_timeout = 10;

    • setOverrideMessageTimeout

      public ProcessingResponse.Builder setOverrideMessageTimeout(com.google.protobuf.Duration.Builder builderForValue)
       When ext_proc server receives a request message, in case it needs more
 time to process the message, it sends back a ProcessingResponse message
 with a new timeout value. When the data plane receives this response
 message, it ignores other fields in the response, just stop the original
 timer, which has the timeout value specified in
 :ref:`message_timeout
 <envoy_v3_api_field_extensions.filters.http.ext_proc.v3.ExternalProcessor.message_timeout>`
 and start a new timer with this ``override_message_timeout`` value and keep the
 data plane ext_proc filter state machine intact.
 Has to be >= 1ms and <=
 :ref:`max_message_timeout <envoy_v3_api_field_extensions.filters.http.ext_proc.v3.ExternalProcessor.max_message_timeout>`
 Such message can be sent at most once in a particular data plane ext_proc filter processing state.
 To enable this API, one has to set ``max_message_timeout`` to a number >= 1ms.
      .google.protobuf.Duration override_message_timeout = 10;

    • mergeOverrideMessageTimeout

      public ProcessingResponse.Builder mergeOverrideMessageTimeout(com.google.protobuf.Duration value)
       When ext_proc server receives a request message, in case it needs more
 time to process the message, it sends back a ProcessingResponse message
 with a new timeout value. When the data plane receives this response
 message, it ignores other fields in the response, just stop the original
 timer, which has the timeout value specified in
 :ref:`message_timeout
 <envoy_v3_api_field_extensions.filters.http.ext_proc.v3.ExternalProcessor.message_timeout>`
 and start a new timer with this ``override_message_timeout`` value and keep the
 data plane ext_proc filter state machine intact.
 Has to be >= 1ms and <=
 :ref:`max_message_timeout <envoy_v3_api_field_extensions.filters.http.ext_proc.v3.ExternalProcessor.max_message_timeout>`
 Such message can be sent at most once in a particular data plane ext_proc filter processing state.
 To enable this API, one has to set ``max_message_timeout`` to a number >= 1ms.
      .google.protobuf.Duration override_message_timeout = 10;

    • clearOverrideMessageTimeout

      public ProcessingResponse.Builder clearOverrideMessageTimeout()
       When ext_proc server receives a request message, in case it needs more
 time to process the message, it sends back a ProcessingResponse message
 with a new timeout value. When the data plane receives this response
 message, it ignores other fields in the response, just stop the original
 timer, which has the timeout value specified in
 :ref:`message_timeout
 <envoy_v3_api_field_extensions.filters.http.ext_proc.v3.ExternalProcessor.message_timeout>`
 and start a new timer with this ``override_message_timeout`` value and keep the
 data plane ext_proc filter state machine intact.
 Has to be >= 1ms and <=
 :ref:`max_message_timeout <envoy_v3_api_field_extensions.filters.http.ext_proc.v3.ExternalProcessor.max_message_timeout>`
 Such message can be sent at most once in a particular data plane ext_proc filter processing state.
 To enable this API, one has to set ``max_message_timeout`` to a number >= 1ms.
      .google.protobuf.Duration override_message_timeout = 10;

    • getOverrideMessageTimeoutBuilder

      public com.google.protobuf.Duration.Builder getOverrideMessageTimeoutBuilder()
       When ext_proc server receives a request message, in case it needs more
 time to process the message, it sends back a ProcessingResponse message
 with a new timeout value. When the data plane receives this response
 message, it ignores other fields in the response, just stop the original
 timer, which has the timeout value specified in
 :ref:`message_timeout
 <envoy_v3_api_field_extensions.filters.http.ext_proc.v3.ExternalProcessor.message_timeout>`
 and start a new timer with this ``override_message_timeout`` value and keep the
 data plane ext_proc filter state machine intact.
 Has to be >= 1ms and <=
 :ref:`max_message_timeout <envoy_v3_api_field_extensions.filters.http.ext_proc.v3.ExternalProcessor.max_message_timeout>`
 Such message can be sent at most once in a particular data plane ext_proc filter processing state.
 To enable this API, one has to set ``max_message_timeout`` to a number >= 1ms.
      .google.protobuf.Duration override_message_timeout = 10;

    • getOverrideMessageTimeoutOrBuilder

      public com.google.protobuf.DurationOrBuilder getOverrideMessageTimeoutOrBuilder()
       When ext_proc server receives a request message, in case it needs more
 time to process the message, it sends back a ProcessingResponse message
 with a new timeout value. When the data plane receives this response
 message, it ignores other fields in the response, just stop the original
 timer, which has the timeout value specified in
 :ref:`message_timeout
 <envoy_v3_api_field_extensions.filters.http.ext_proc.v3.ExternalProcessor.message_timeout>`
 and start a new timer with this ``override_message_timeout`` value and keep the
 data plane ext_proc filter state machine intact.
 Has to be >= 1ms and <=
 :ref:`max_message_timeout <envoy_v3_api_field_extensions.filters.http.ext_proc.v3.ExternalProcessor.max_message_timeout>`
 Such message can be sent at most once in a particular data plane ext_proc filter processing state.
 To enable this API, one has to set ``max_message_timeout`` to a number >= 1ms.
      .google.protobuf.Duration override_message_timeout = 10;
      Specified by:
      getOverrideMessageTimeoutOrBuilder in interface ProcessingResponseOrBuilder

    • setUnknownFields

      public final ProcessingResponse.Builder setUnknownFields(com.google.protobuf.UnknownFieldSet unknownFields)
      Specified by:
      setUnknownFields in interface com.google.protobuf.Message.Builder
      Overrides:
      setUnknownFields in class com.google.protobuf.GeneratedMessageV3.Builder<ProcessingResponse.Builder>

    • mergeUnknownFields

      public final ProcessingResponse.Builder mergeUnknownFields(com.google.protobuf.UnknownFieldSet unknownFields)
      Specified by:
      mergeUnknownFields in interface com.google.protobuf.Message.Builder
      Overrides:
      mergeUnknownFields in class com.google.protobuf.GeneratedMessageV3.Builder<ProcessingResponse.Builder>