Skip to content

http: require stream_error_on_invalid_http_messaging to be set for every HCM #9846

@mattklein123

Description

@mattklein123

As documented in https://www.envoyproxy.io/docs/envoy/latest/configuration/best_practices/level_two, @alyssawilk and I have discussed forcing the user to specify an HCM configuration option that specifies how to handle stream errors, thus guiding users into selecting the correct option for their use case. I think the best way of doing this is:

  1. Add a new option to configure this setting using a bool WKT, deprecate the old option, and explicitly warn/stat if the new option is not set at all, telling the user that in a future version this setting will be required.
  2. In the normal "deprecation cycle" make the new setting required.

Metadata

Metadata

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions