{"version":"2.1.310","anchor":"proxy-settings-applied-to-code-sign-and-jwks-fetches","canonical_anchor":"proxy-settings-applied-to-code-sign-and-jwks-fetches","heading":"Commit signing and token checks pass an extra connection setting","tier":"internal","area":"Git","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310\/e\/proxy-settings-applied-to-code-sign-and-jwks-fetches","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310","markdown":"### Commit signing and token checks pass an extra connection setting\n\nRequests for commit signing and for the keys used to check tokens now carry an extra connection setting, and a token error message is fixed\n\n**Unclear.** It is not confirmed that the extra connection setting is the proxy or TLS configuration.\n\n**What**\n\nTwo network requests now carry an extra connection setting alongside the address they go to:\n\n- `sign-commit`, the request that asks for a commit to be signed\n\n- `decode-token`, when it downloads the public keys used to check a login token (these keys are known as JWKS)\n\nThe error message `decode-token` shows when that key download fails also had a mix-up corrected, so it reports the right detail.\n\n**Why**\n\nIf the extra setting is how Claude Code applies its proxy or network settings, these two requests may now work on networks that send traffic through a corporate proxy. A proxy is a server that all outgoing web traffic has to pass through.\n\n- Area: Git\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}