{"version":"2.1.310","anchor":"gateway-discovery-request-and-ca-certs","canonical_anchor":"gateway-discovery-request-and-ca-certs","heading":"Gateway requests may now use custom certificate settings","tier":"notice","area":"Elsewhere","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310\/e\/gateway-discovery-request-and-ca-certs","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310","markdown":"### Gateway requests may now use custom certificate settings\n\nGateway model discovery and gateway host checks now pass extra connection and certificate options, likely for custom certificate setups\n\n**Unclear.** It is not clear whether custom certificate settings now fully apply to gateway model discovery and managed settings requests.\n\n**What**\n\nA gateway is a server some organisations put between Claude Code and the model's API. Several changes touch how Claude Code connects to one:\n\n- Looking up available models through the gateway now sends extra connection options.\n\n- The gateway host check now passes CA certificates, the files that tell Claude Code which secure servers to trust.\n\n- Secure connections now build their list of trusted certificates in a different way.\n\n**Why**\n\nThis matters to company users whose network uses its own certificates. Gateway and managed settings requests may now respect that setup.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: org\n- Heads-up: no"}