Skip to content

A42 update: header hash policy behaves the same as route header matching #392

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

Merged
merged 1 commit into from
Sep 7, 2023
Merged

A42 update: header hash policy behaves the same as route header matching #392

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion A42-xds-ring-hash-lb-policy.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -72,7 +72,11 @@ Here is how gRPC will handle each type of hash policy:

- [`header`](https://github.com/envoyproxy/envoy/blob/2443032526cf6e50d63d35770df9473dd0460fc0/api/envoy/config/route/v3/route_components.proto#L710):
gRPC will support this type of hash policy. This allows hashing on a
request header.
request header. The header matching logic will behave the same way as
specified for route matching, as per [gRFC
A28](https://github.com/grpc/proposal/blob/master/A28-xds-traffic-splitting-and-routing.md#picking)
(i.e., it will ignore headers with a `-bin` suffix and may need
special handling for `content-type`).
- [`cookie`](https://github.com/envoyproxy/envoy/blob/2443032526cf6e50d63d35770df9473dd0460fc0/api/envoy/config/route/v3/route_components.proto#L713):
gRPC does not support HTTP cookies, so we will not support this hash
policy. If specified, this policy will not return any result.
Expand Down