Skip to content

Documentation and behavior don't match, for HttpProtocolOptions::explicit_http_config #38064

New issue
New issue
Closed
Closed
Documentation and behavior don't match, for HttpProtocolOptions::explicit_http_config#38064
Labels
apiarea/docsarea/protobufstalestalebot believes this issue/PR has not been touched recently
@ravenblackx

Description

@ravenblackx
ravenblackx
opened on Jan 16, 2025

envoy/api/envoy/extensions/upstreams/http/v3/http_protocol_options.proto

Lines 142 to 143 in d34e163

// To explicitly configure either HTTP/1 or HTTP/2 (but not both!) use ``explicit_http_config``.
// If the ``explicit_http_config`` is empty, HTTP/1.1 is used.

Actual behavior if explicit_http_config is empty:
Proto constraint validation failed (HttpProtocolOptionsValidationError.ExplicitHttpConfig: embedded message failed validation | caused by field: "protocol_config", reason: is required): explicit_http_config

Metadata

Metadata

Assignees

No one assigned

    Labels

    apiarea/docsarea/protobufstalestalebot believes this issue/PR has not been touched recently

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions