Expand description
Custom request, response, and trailing metadata.
gRPC distinguishes “ASCII metadata” (printable-ASCII values) from “binary
metadata” (key ends in -bin, value base64-encoded on the wire). Reserved
keys (grpc-*, te, content-type, user-agent, HTTP/2 pseudo-headers)
are owned by the framework and rejected on insert.
Metadata is an ordered map that round-trips through
trillium::Headers. It backs Status::metadata,
the trailing metadata sent alongside an error status.
Structs§
- Metadata
- An ordered, multi-valued map of custom gRPC metadata. Keys may repeat;
insertion order is preserved through the round-trip to and from
trillium::Headers.
Enums§
- Metadata
Error - Why an insert into
Metadatawas rejected. - Metadata
Value - A single metadata value: either printable ASCII text or, for
-binkeys, raw bytes (base64-encoded on the wire).