Bypass SWG for multi-domain web apps, SSO, CDNs & APIs on Mac

Why bypassing a single root domain is not enough for modern apps—discover login, CDN, and API hostnames in SWG bar and reset keep-alive connections cleanly.

SWG bar · Updated

A common surprise when enabling Bypass SWG on macOS is seeing the main webpage reload while sign-in redirects, images, package downloads, or API calls still hit HTTPS inspection or fail. Because SWG bar applies bypass rules per exact hostname, multi-domain web apps and developer tools often depend on several separate hosts.

Why single-hostname bypass does not cover subdomains

Enabling bypass on app.example.com routes only app.example.com. It does not automatically bypass:

  • Single sign-on (SSO) & OAuth providers: login.example.com, auth.example.com, sso.company.com, or third-party identity hosts (accounts.google.com, login.microsoftonline.com).
  • API & AI endpoints: api.example.com, graphql.example.com, or separate telemetry/streaming subdomains.
  • Static assets & registries: cdn.example.net, assets.example.com, or object storage buckets (*.s3.amazonaws.com, objects.githubusercontent.com).

Note that unidentifiable or encrypted SNI/ECH hostnames cannot be matched for per-domain bypass.

Find every inspected hostname used by an app

  1. Open the website or run the failing developer workflow once while SWG bar is monitoring.
  2. In SWG bar → Domains, sort or filter by Confirmed / Suspected and search by keyword (for example example or auth), or query via the CLI:
swgbar domains list --status confirmed --search example
swgbar domains list --bypass active
  1. For each inspected hostname required by the workflow, open its details and enable Bypass SWG (or run swgbar bypass enable <hostname>).
  2. Remember that bypassing one authentication or API domain on an authorized network does not mean every unrelated domain needs bypass—keep rules scoped strictly to the specific hosts that require it.

Close keep-alive connections and check Chrome status

Even after Bypassing appears, browsers and background daemons reuse existing HTTP/2, HTTP/3, or TLS keep-alive sockets over the old inspected path:

  • Web browsers: Reload the affected tab (Cmd + Shift + R), or close and reopen the browser window if the site uses long-lived WebSocket or HTTP/3 connections. Use the Chrome companion extension to check the active hostname shown for the current tab—though remember the extension displays recorded SWG bar observations rather than inspecting Chrome’s live socket.
  • Terminal & IDEs: Restart long-running processes (npm, Claude Code daemon, IDE language servers, or git credential helpers) so they open fresh TCP/TLS connections over the physical interface.

Verify each hostname separately

After updating rules, open Domains (or run swgbar domains detail <hostname>) and verify fresh probes confirm public trust for each hostname in the workflow—not just the top-level URL shown in the browser address bar. If an organization-wide SaaS or SSO domain affects everyone on the team, compare whether an administrator policy exception is better suited in SWG bypass vs. TLS inspection exception.