apollographql / apollographql/federation

Gateway: Set `User-Agent` when talking to downstream services.

Open
#337 2 comments 2 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
725
Forks
276
Avg merge
1h 47m
Merged PRs (30d)
1

Description

It seems that, by default, it would be reasonable for `@apollo/gateway` to set a `User-agent` header when talking to downstream services which indicates that its name and version along with some other `process` details like Platform. (e.g., `Apollo Gateway/0.16.7 Node.js/12.x.x Linux/??`).

## TODO

- [ ] Determine / propose exactly which parameters to include prior to opening a PR. 😉
- [ ] While Apollo Gateway doesn't automatically pass headers to downstream services, anyone who did implement that themselves would risk squashing this header. In that implementation, so long as _that other_ header survives, that seems reasonable.

Contributor guide

Open the contributing guide

Research direction

The issue names no source files, tests, or entry points. First clarify which User-Agent parameters and header-preservation behavior are required before locating the gateway's downstream request path. Done means the parameter set and expected behavior are agreed and covered by the relevant tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
graphql, node.js, typescript
Domain
api, backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.