Firebase Admin Node httpAgent: Proxy Coverage by Service
Identify which Firebase Admin Node operations consume the configured HTTP agent before assuming all SDK traffic uses the same proxy.
An authentication call works through the proxy, but a database connection fails. In a Firebase application, that can be a transport difference rather than an intermittent proxy.
The Admin Node SDK's httpAgent application option applies to services that make REST calls, including Auth and Messaging. Its documented scope excludes Realtime Database and Firestore. Credential objects also have their own agent configuration through the corresponding credential factory methods.
| Failing operation | Configuration to inspect |
|---|---|
| An Admin REST service call | The application's HTTP agent |
| Acquiring a credential token | The credential object's HTTP configuration |
| A database connection | The database client's own transport support |
This is why adding an agent to initialization cannot certify that every later connection takes the same route. Record the failing service and destination before changing a configuration that already works for another service.
Old discussions also mix the Firebase command-line tool with application SDKs. A CLI fix for reading http_proxy does not establish that a database client inside your Node process uses that same option.
Use the supported configuration interface for the transport you actually need. Patching a nested WebSocket dependency may appear to affect one connection while leaving another path unchanged, and it makes a future dependency update harder to reason about.