How to Bypass HTTPS & TLS Inspection on macOS (Break-and-Inspect Guide)

Bypass HTTPS and TLS break-and-inspect decryption on macOS per domain with SWG bar: how TLS termination breaks HTTP/2, QUIC, and pinning, plus CLI verification.

SWG bar · Updated

To bypass HTTPS or TLS inspection (break-and-inspect) for a specific domain on macOS without disabling your security client globally, open SWG bar → Domains, select the hostname, and enable Bypass SWG (or run swgbar bypass enable <domain>). Wait until the row displays Bypassing, then restart the browser tab, IDE, or CLI session so a fresh TLS handshake establishes over your Mac’s physical Hardware IPv4 interface.

Enterprise Secure Web Gateways (SWGs) and next-generation firewalls inspect HTTPS traffic by acting as a trusted man-in-the-middle: they terminate your Mac’s outbound TLS 1.2/1.3 handshake, inspect decrypted HTTP payloads, and re-encrypt traffic to the origin server. While browsers silently accept the gateway’s MDM-installed root CA, modern protocols and strict developer clients frequently break under TLS re-signing.

What HTTPS / TLS break-and-inspect actually breaks on a Mac

Even when your Mac trusts the enterprise root certificate in Keychain, inline TLS termination disrupts four common macOS workflows:

  1. Certificate pinning and mutual TLS (mTLS): Apps that pin the origin server’s public key or present a client certificate abort the handshake the moment a gateway substitutes its own leaf certificate. See Certificate pinning and mTLS under SWG inspection.
  2. HTTP/3 (QUIC) and long-lived HTTP/2 or WebSocket streams: Gateways that downgrade or proxy TLS connections often drop UDP QUIC streams, stall streaming LLM responses, or reset persistent IDE/WebSocket channels.
  3. Independent CLI and language CA stores: Runtimes such as Node.js, Python, Git, Homebrew, Docker, Claude Code, and Cursor ship bundled root CA stores and fail with CERTIFICATE_VERIFY_FAILED or UNABLE_TO_GET_ISSUER_CERT_LOCALLY.
  4. Latency-sensitive developer APIs: Backhauling every TLS handshake through a distant cloud SWG PoP adds round-trip overhead to package installs, git fetches, and real-time code completion.

Per-domain TLS bypass vs. local proxy settings and gateway exceptions

Aspect Per-domain bypass (SWG bar) Admin TLS inspection exception (Do Not Decrypt) Local proxy edits (System Settings → Proxies)
Layer Hostname-level physical IPv4 routing via macOS NetworkExtension Central SWG / firewall decryption policy Explicit OS HTTP/HTTPS proxy fields only
Works against transparent SWGs? Yes, when a physical IPv4 path is reachable Yes (configured by IT) No — ignored or overwritten by utun / transparent SWG agents
Requires IT admin console? No (local control on authorized Mac) Yes (Zscaler, Netskope, Cloudflare, Palo Alto admin portal) No
Preserves device posture / SSO? Yes — corporate endpoint agent stays running Yes Often breaks corporate PAC routing

For an architectural deep dive comparing route changes and gateway decryption exclusions, see SWG bypass vs. TLS inspection exception.

Bypass HTTPS & TLS inspection for a domain on macOS

  1. Identify every inspected hostname: Open SWG bar → Domains or run swgbar domains list --status confirmed via the CLI. Remember that example.com, auth.example.com, and api.example.com are separate hostnames.
  2. Enable per-domain bypass: Click Enable in the domain’s Bypass SWG row, or run:
swgbar bypass enable api.example.com
swgbar bypass status
  1. Close pooled TLS and HTTP/3 connections: Refreshing a single browser tab can reuse an existing pooled HTTP/2 or QUIC socket from the inspected path. SWG bar’s native bypass falls back HTTP/3 to HTTPS over TCP on new connections, so reload the tab or quit and reopen the target app after Bypassing appears.
  2. Verify the fresh certificate chain: Run swgbar probe api.example.com (or openssl s_client -connect api.example.com:443 -servername api.example.com -showcerts </dev/null) to verify the origin server’s public issuer is returned.

If Recovering or Paused appears instead of Bypassing, check Troubleshoot Recovering, Paused, and bypass states on macOS.

Turn off bypass or fall back to CA trust when required

Click the active Bypass SWG control again—or run swgbar bypass disable <domain>—to return a hostname to standard gateway routing immediately. Quitting SWG bar also stops active bypass right away while remembering your saved hostname selections for next launch.

If your network blocks direct outbound IPv4 traffic at the firewall level, disable bypass and use CLI & AI tool CA trust fixes or request an administrator Do Not Decrypt rule for the exact hostname.