We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Title: Add a max length field to String Matcher
Description:
Currently we use a regex to limit the max header length, but a simpler "max length" field would reduce the need for initializing the RegexMatcher.
RegexMatcher
Protobuf in question: string.proto
string.proto
The text was updated successfully, but these errors were encountered:
+1 sounds like a good idea to me. Another place to add this could be in https://www.envoyproxy.io/docs/envoy/latest/api-v3/config/http/header_validators. If the motivation is to reduce overall header data, it might be better to enforce that at the protocol level.
Sorry, something went wrong.
We're specifically trying to limit the length of XFF headers to avoid infinite forwarding loops by returning a 431, so maybe?
@kyessenov should I create a PR for the string.proto or https://www.envoyproxy.io/docs/envoy/latest/api-v3/extensions/http/header_validators/envoy_default/v3/header_validator.proto#extensions-http-header-validators-envoy-default-v3-headervalidatorconfig?
No branches or pull requests
Title: Add a max length field to String Matcher
Description:
Currently we use a regex to limit the max header length, but a simpler "max length" field would reduce the need for initializing the
RegexMatcher
.Protobuf in question:
string.proto
The text was updated successfully, but these errors were encountered: