-
Notifications
You must be signed in to change notification settings - Fork 4.4k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Add support for String Matcher in Header Matching #6226
Comments
This may impact the other languages - in K8S Gateway/GAMMA 'exact' is the only supported header matcher in core ( plus a regex with unspecified syntax ). It is pretty bad as it prevents the use of the new API ( at least in Istio - but I suspect in any other XDS implementation ) |
We have had a couple of requests in the past to add support for We are having a cross-language discussion right now to see what it would take to add support for |
We will add support for this soon. Please see grpc/proposal#359. |
Thanks - we have to add support for this and for all languages, otherwise
we can't support Gateway/GAMMA ( or Istio ) API.
…On Wed, May 3, 2023 at 12:33 PM Easwar Swaminathan ***@***.***> wrote:
We will add support for this soon. Please see grpc/proposal#359
<grpc/proposal#359>.
—
Reply to this email directly, view it on GitHub
<#6226 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAUR2QTR6Y7JBC5SNXYLTDXEKXJJANCNFSM6AAAAAAXNCPCEI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
The PR is still in flight. We can kick off once proposal finally merged. |
Do we need to implement StringMatcher for RBAC? grpc-go/internal/xds/rbac/matchers.go Line 267 in f2fbb0e
|
Ah, yes we do. I spoke to the other languages and they have this for RBAC. Thanks for bringing this up. I'll file an issue. |
Filed #6369. |
Sent #6419 to add support for string matcher in RBAC header matching. Thanks for bringing this up. |
This is produced by a standard HttpRoute -
NOTE: if you are reporting is a potential security vulnerability or a crash,
please follow our CVE process at
https://github.com/grpc/proposal/blob/master/P4-grpc-cve-process.md instead of
filing an issue here.
Please see the FAQ in our main README.md, then answer the questions below
before submitting your issue.
What version of gRPC are you using?
v1.56.0-dev ( tried on older versions too )
What version of Go are you using (
go version
)?What operating system (Linux, Windows, …) and version?
What did you do?
If possible, provide a recipe for reproducing the error.
What did you expect to see?
What did you see instead?
The text was updated successfully, but these errors were encountered: