示例
google.golang.org/grpc v1.83.0: Preserve caller-supplied outgoing gRPC metadata when a unary client interceptor adds its own metadata
已验证示例 — golang google.golang.org/grpc v1.83.0: Preserve caller-supplied outgoing gRPC metadata when a unary client interceptor adds its own metadata.…
sha256:a8acd8ef9a84180020f012467fae967f3de130dff4d432708ac5bf0a6df64717
本网络只提供一件事：能构建的样本。它在沙箱中运行并保留签名回执。它不评级、不担保——同样的代码能否在你的环境构建，它没有测量过。
提交了通过的契约回执的不同签名密钥数量。为 1 表示只有作者；大于 1 表示还有其他人构建过。密钥是自行生成的，背后没有注册身份，因此计的是密钥而非人。
MIT-0
执行证据
声明的环境与签名的运行分开呈现，你可以看到这个样本究竟运行了什么、在哪里运行。
- 证据依据
- 签名契约通过
- 验证回执
- 2
- 构建过它的签名密钥
- 2
声明的环境
go 1.26 linux x64 go 1.26 go go
验证运行环境
| 环境 | 契约 | 阶段 | 运行日期 |
|---|---|---|---|
| go 1.26 · linux alpine/x64 · docker ed25519:d91480838ac982c9 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · golang@1 |
2026-08-17 |
| go 1.26 · linux alpine/x64 · docker ed25519:2175b912ea1c23b1 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · golang@1 |
2026-08-18 |
案例
HOW- 目标
- Preserve caller-supplied outgoing gRPC metadata when a unary client interceptor adds its own metadata
- 符号
-
- google.golang.org/grpc.NewServer
- google.golang.org/grpc.Server.RegisterService
- google.golang.org/grpc.NewClient
- google.golang.org/grpc.WithContextDialer
- google.golang.org/grpc.WithTransportCredentials
- google.golang.org/grpc.WithUnaryInterceptor
- google.golang.org/grpc.ClientConn.Invoke
- google.golang.org/grpc/test/bufconn.Listen
- google.golang.org/grpc/metadata.NewOutgoingContext
- google.golang.org/grpc/metadata.AppendToOutgoingContext
- google.golang.org/grpc/metadata.FromIncomingContext
- google.golang.org/grpc/status.Code
- 环境
- go 1.26
- 创建时间
- 2026-08-17T01:31:28Z
契约
- 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