Package io.envoyproxy.envoy.config.core.v3

Interface Http1ProtocolOptions.HeaderKeyFormatOrBuilder

All Superinterfaces:
com.google.protobuf.MessageLiteOrBuilder, com.google.protobuf.MessageOrBuilder
All Known Implementing Classes:
Http1ProtocolOptions.HeaderKeyFormat, Http1ProtocolOptions.HeaderKeyFormat.Builder
Enclosing class:
Http1ProtocolOptions
public static interface Http1ProtocolOptions.HeaderKeyFormatOrBuilder extends com.google.protobuf.MessageOrBuilder

  • Method Details

    • hasProperCaseWords

      boolean hasProperCaseWords()
       Formats the header by proper casing words: the first character and any character following
 a special character will be capitalized if it's an alpha character. For example,
 ``"content-type"`` becomes ``"Content-Type"``, and ``"foo$b#$are"`` becomes ``"Foo$B#$Are"``.

 .. note::

   While this results in most headers following conventional casing, certain headers
   are not covered. For example, the ``"TE"`` header will be formatted as ``"Te"``.
      .envoy.config.core.v3.Http1ProtocolOptions.HeaderKeyFormat.ProperCaseWords proper_case_words = 1;
      Returns:
      Whether the properCaseWords field is set.

    • getProperCaseWords

      Http1ProtocolOptions.HeaderKeyFormat.ProperCaseWords getProperCaseWords()
       Formats the header by proper casing words: the first character and any character following
 a special character will be capitalized if it's an alpha character. For example,
 ``"content-type"`` becomes ``"Content-Type"``, and ``"foo$b#$are"`` becomes ``"Foo$B#$Are"``.

 .. note::

   While this results in most headers following conventional casing, certain headers
   are not covered. For example, the ``"TE"`` header will be formatted as ``"Te"``.
      .envoy.config.core.v3.Http1ProtocolOptions.HeaderKeyFormat.ProperCaseWords proper_case_words = 1;
      Returns:
      The properCaseWords.

    • getProperCaseWordsOrBuilder

      Http1ProtocolOptions.HeaderKeyFormat.ProperCaseWordsOrBuilder getProperCaseWordsOrBuilder()
       Formats the header by proper casing words: the first character and any character following
 a special character will be capitalized if it's an alpha character. For example,
 ``"content-type"`` becomes ``"Content-Type"``, and ``"foo$b#$are"`` becomes ``"Foo$B#$Are"``.

 .. note::

   While this results in most headers following conventional casing, certain headers
   are not covered. For example, the ``"TE"`` header will be formatted as ``"Te"``.
      .envoy.config.core.v3.Http1ProtocolOptions.HeaderKeyFormat.ProperCaseWords proper_case_words = 1;

    • hasStatefulFormatter

      boolean hasStatefulFormatter()
       Configuration for stateful formatter extensions that allow using received headers to
 affect the output of encoding headers. E.g., preserving case during proxying.
 [#extension-category: envoy.http.stateful_header_formatters]
      .envoy.config.core.v3.TypedExtensionConfig stateful_formatter = 8;
      Returns:
      Whether the statefulFormatter field is set.

    • getStatefulFormatter

      TypedExtensionConfig getStatefulFormatter()
       Configuration for stateful formatter extensions that allow using received headers to
 affect the output of encoding headers. E.g., preserving case during proxying.
 [#extension-category: envoy.http.stateful_header_formatters]
      .envoy.config.core.v3.TypedExtensionConfig stateful_formatter = 8;
      Returns:
      The statefulFormatter.

    • getStatefulFormatterOrBuilder

      TypedExtensionConfigOrBuilder getStatefulFormatterOrBuilder()
       Configuration for stateful formatter extensions that allow using received headers to
 affect the output of encoding headers. E.g., preserving case during proxying.
 [#extension-category: envoy.http.stateful_header_formatters]
      .envoy.config.core.v3.TypedExtensionConfig stateful_formatter = 8;

    • getHeaderFormatCase

      Http1ProtocolOptions.HeaderKeyFormat.HeaderFormatCase getHeaderFormatCase()