{"version":"2.1.295","anchor":"gateway-forwards-upstream-request-id","canonical_anchor":"gateway-forwards-upstream-request-id","heading":"The gateway now passes along the upstream request ID","tier":"internal","area":"LLM Gateway","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/gateway-forwards-upstream-request-id","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### The gateway now passes along the upstream request ID\n\nThe gateway now reads an upstream request ID header, returns it as the request ID on successful replies, and passes on a response timeout\n\n**What**\n\nIn the gateway, the part that relays requests between Claude Code and the model service:\n\n- It reads a new `x-gateway-upstream-request-id` header and removes it from the request.\n\n- It sets a `request-id` header on successful replies.\n\n- It passes on a timeout for how long to wait for the first part of a reply, taken from the timeouts an operator has set.\n\n**Why**\n\nRequests through the gateway can be traced more easily, and its timeouts follow the operator's settings.\n\n- Area: LLM Gateway\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: no"}