{"version":"2.1.311","anchor":"url-check-returns-the-protocol-not-only-https","canonical_anchor":"url-check-returns-the-protocol-not-only-https","heading":"A URL check no longer rejects every address that is not https","tier":"internal","area":"Network Proxy","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/url-check-returns-the-protocol-not-only-https","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### A URL check no longer rejects every address that is not https\n\nA URL check now returns the address's protocol when an allow check passes, instead of rejecting anything that is not https up front\n\n**Unclear.** Which parts of Claude Code use this check, and so whether plain `http` addresses are now accepted anywhere, is not established.\n\n**What**\n\nA URL check in Claude Code used to reject any web address that did not start with `https:`. It no longer does that up front. Instead, it reports the address's protocol, such as `http:` or `https:`, when a separate allow check passes, and reports nothing when it fails.\n\n**Why**\n\nThe code that uses this check can now tell `http` and `https` addresses apart. This may mean some plain `http` addresses, such as ones pointing at your own machine, are accepted where they were refused before.\n\n- Area: Network Proxy\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}