Chrome Proxy Bypass for One Scheme and Port
Use a supported Chromium manual bypass pattern when only one scheme and port should avoid the configured proxy.
To keep only an HTTPS API on port 8443 direct, add a scheme-and-port rule to an existing Chromium fixed-server extension configuration:
bypassList: [
"https://api.office.example:8443"
]This is the rules fragment. Retain the surrounding permissions, mode, proxy endpoint and completion handling. The rule selects that scheme, hostname and port; an application path is not another matching field in this syntax.
Keep the boundaries beside the intended match:
- The same hostname on another port should retain its intended proxy route.
- Another scheme must be checked separately.
- A related subdomain is another destination to check.
If those requests unexpectedly go direct, inspect the browser's effective proxy configuration for other exceptions, including host-wide, suffix and implicit local rules. Adding one narrow entry does not remove a broader exception elsewhere.
This grammar belongs to the applicable Chromium interface. Another program's NO_PROXY parser may use different port syntax or lack that selection feature.
After confirming the selected route, check that the client can reach the direct service and trust its certificate. A matching bypass can reveal a missing local route or trust setup previously handled by the proxy path.