Check before promising
Browser permissions and local-app behavior must pass compatibility checks before setup continues.
Compatibility path
The browser path is limited to compatible HTTP behavior. Sessions, WebSockets, streaming, arbitrary headers, and other unsupported cases require the portable connector.
See how it worksBrowser permissions and local-app behavior must pass compatibility checks before setup continues.
The browser path does not forward browser credentials, visitor cookies, or Set-Cookie responses.
When browser compatibility is insufficient, the same intended route configuration continues through the connector path.