示例
Preserve caller-supplied outgoing gRPC metadata when a unary client interceptor adds its own metadata
sha256:a8acd8ef9a84180020f012467fae967f3de130dff4d432708ac5bf0a6df64717
PUBLISHED
L3_CONTRACT_PASS
MIT-0
案例
- 目标
- Preserve caller-supplied outgoing gRPC metadata when a unary client interceptor adds its own metadata HOW
- 包
- google.golang.org/grpc v1.83.0 google.golang.org/protobuf v1.36.11
- 环境
- go 1.26
- 创建时间
- 2026-08-17T01:31:28Z
常见的想当然
A unary client interceptor can call metadata.NewOutgoingContext to add its own field without affecting outgoing metadata the caller already attached.
这是本样本作者记下的、开发者或模型在此处通常会有的预期。下面的契约才是真正运行过的东西。
契约
- A grpc.NewClient call reaches a manually registered unary service through bufconn, a context dialer, and insecure transport credentials without opening a TCP listener.
- When a unary client interceptor uses metadata.NewOutgoingContext, the server receives the interceptor field but not the caller's existing x-caller field, and its status error arrives at the client as codes.Unauthenticated.
- When the interceptor uses metadata.AppendToOutgoingContext instead, metadata.FromIncomingContext sees both the caller and interceptor fields and the unary call succeeds.
文件
- NOTES.md
- csx.json
- go.mod
- go.sum
- metadata_interceptor_test.go
下载已验证的构件 (tar.gz) — 契约实际运行的那些字节
原始种子者
验证回执
- go 1.26 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · golang@1 · 2026-08-17 · ed25519:d91480838ac982c9