Skip to content
This repository was archived by the owner on Apr 9, 2021. It is now read-only.
This repository was archived by the owner on Apr 9, 2021. It is now read-only.

Document application best practices for user-agent #380

@nathanielmanistaatgoogle

Description

Applications can customize the user-agent header that will be used with their RPCs (by means of channel arguments in the core-wrapping languages), but we offer no guidance on what applications should do. grpc.primary_user_agent and grpc.secondary_user_agent are different things, and each can be specified multiple times in a single grpc_channel_args value; what does that all mean?

Also it was a complete surprise to me that if an application tries to set the user-agent as though it were an ordinary piece of metadata, it gets eaten by the core and not sent on the wire - we should make that clear too.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions