We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Go inverts the match result directly:
grpc-go/internal/xds/rbac/matchers.go
Lines 288 to 290 in 6f2a922
However, the Envoy behavior is to invert the operation, such that == becomes != and both fail for a missing entry: https://github.com/envoyproxy/envoy/blob/b7393b0bd221dab43bea0d697df0954a5b01d7d7/source/common/http/header_utility.cc#L140-L146
==
!=
This was implemented appropriately in Java. I'll add some language to call this out in the gRFC.
The text was updated successfully, but these errors were encountered:
A41: Call out precise HeaderMatcher.invert_match semantics
23c2cf8
The proper behavior is subtle and easy to assume incorrectly. This caused a bug in Go (grpc/grpc-go#4896) and would be easy for other implementations to assume incorrectly. As determined by Envoy's behavior: https://github.com/envoyproxy/envoy/blob/7d3e444d757696c15a4020b1d2d8ba5cb7f12501/source/common/http/header_utility.cc#L140-L146
fixed by #4902
Sorry, something went wrong.
zasweq
Successfully merging a pull request may close this issue.
Go inverts the match result directly:
grpc-go/internal/xds/rbac/matchers.go
Lines 288 to 290 in 6f2a922
However, the Envoy behavior is to invert the operation, such that
==
becomes!=
and both fail for a missing entry:https://github.com/envoyproxy/envoy/blob/b7393b0bd221dab43bea0d697df0954a5b01d7d7/source/common/http/header_utility.cc#L140-L146
This was implemented appropriately in Java. I'll add some language to call this out in the gRFC.
The text was updated successfully, but these errors were encountered: