Class PathTransformation.Operation.NormalizePathRFC3986.Builder

java.lang.Object
com.google.protobuf.AbstractMessageLite.Builder
com.google.protobuf.AbstractMessage.Builder<PathTransformation.Operation.NormalizePathRFC3986.Builder>
com.google.protobuf.GeneratedMessage.Builder<PathTransformation.Operation.NormalizePathRFC3986.Builder>
io.envoyproxy.envoy.type.http.v3.PathTransformation.Operation.NormalizePathRFC3986.Builder
All Implemented Interfaces:
com.google.protobuf.Message.Builder, com.google.protobuf.MessageLite.Builder, com.google.protobuf.MessageLiteOrBuilder, com.google.protobuf.MessageOrBuilder, PathTransformation.Operation.NormalizePathRFC3986OrBuilder, Cloneable
Enclosing class:
PathTransformation.Operation.NormalizePathRFC3986

public static final class PathTransformation.Operation.NormalizePathRFC3986.Builder extends com.google.protobuf.GeneratedMessage.Builder<PathTransformation.Operation.NormalizePathRFC3986.Builder> implements PathTransformation.Operation.NormalizePathRFC3986OrBuilder
 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>`_
 
Protobuf type envoy.type.http.v3.PathTransformation.Operation.NormalizePathRFC3986