The self-hosted gateway strips your client's API key before calling upstream providers.
What's wrong with this entry?
Every path where the self-hosted gateway attaches its own operator credential to an upstream provider request now deletes the inbound authorization and x-api-key headers first, so a key supplied by the client can no longer reach the upstream alongside the gateway's own.
(r.delete("authorization"), r.delete("x-api-key"));
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.227
claude gatewaynow identifies itself as the gateway providerBoth mention gateway
-
v2.1.229
Gateway streaming keeps connections alive with pings
Both mention gateway
-
v2.1.232
Cloud gateway sign-in explains its restart, and refuses when it cannot
Both mention gateway