package envoy.type.http.v3

Get desktop application:
View/edit binary Protocol Buffers messages

Cookie defines an API for obtaining or generating HTTP cookie.

Used in: extensions.http.stateful_session.cookie.v3.CookieBasedSessionState

• string name = 1

  The name that will be used to obtain cookie value from downstream HTTP request or generate new cookie for downstream.

• optional google.protobuf.Duration ttl = 2

  Duration of cookie. This will be used to set the expiry time of a new cookie when it is generated. Set this to 0s to use a session cookie and disable cookie expiration.

• string path = 3

  Path of cookie. This will be used to set the path of a new cookie when it is generated. If no path is specified here, no path will be set for the cookie.

Used in: extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.PathNormalizationOptions

• repeated PathTransformation.Operation operations = 1

  A list of operations to apply. Transformations will be performed in the order that they appear.

A type of operation to alter text.

Used in: PathTransformation

• oneof operation_specifier

  • Operation.NormalizePathRFC3986 normalize_path_rfc_3986 = 2

    Enable path normalization per RFC 3986.

  • Operation.MergeSlashes merge_slashes = 3

    Enable merging adjacent slashes.

Determines if adjacent slashes are merged into one. A common use case is for a request path header. Using this option in ``:ref: PathNormalizationOptions <envoy_v3_api_msg_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.PathNormalizationOptions>`` will allow incoming requests with path ``//dir///file`` to match against route with ``prefix`` match set to ``/dir``. When using for header transformations, note that slash merging is not part of `HTTP spec <https://tools.ietf.org/html/rfc3986>`_ and is provided for convenience.

Used in: Operation

(message has no fields)

Should text be normalized according to RFC 3986? This typically is used for path headers before any processing of requests by HTTP filters or routing. This applies percent-encoded normalization and path segment normalization. Fails on characters disallowed in URLs (e.g. NULLs). See `Normalization and Comparison <https://tools.ietf.org/html/rfc3986#section-6>`_ for details of normalization. Note that this options does not perform `case normalization <https://tools.ietf.org/html/rfc3986#section-6.2.2.1>`_

Used in: Operation

(message has no fields)