Proxy
Take control of your network traffic with Appetize's advanced proxy support. Effortlessly reroute your traffic for better access control, privacy, and security.
Our current support is limited to HTTP Proxies. When your app makes HTTPS connections, the data remains encrypted despite the unencrypted connection to the proxy. The app sends a CONNECT request to the proxy for the destination HTTPS server, initiating an SSL handshake. The proxy acts as a TCP connection forwarder, ensuring end-to-end encryption for app data.
App Level Proxy
Appetize supports settings a proxy server on a per-app basis.
App-Level proxy settings will override the Account default proxy. if you always want the Account-level proxy to be used, use forced proxy instead.
To allow Appetize to proxy all the network events, you need to specify a proxy server to route network traffic to:
With Query Parameter
Add the proxy query parameter to your app or embed URL with your URL encoded proxy server's address (e.g. http://example.com:8080/)as value.
See Query Params Reference for more information.
With JavaScript SDK
Set proxy to http://example.com:8080/ in the configuration e.g.
See Configuration for more information.
Organization Level Proxy
Organization Level Proxy is only available on our Premium and Enterprise plans. Contact us to learn more.
You may also set organization-wide proxy settings by navigating to Organization -> Proxy settings.
Default Proxy
By setting a default proxy, the proxy will be used when no other proxy is specified.
Forced Proxy
By setting a forced proxy, the proxy will be used regardless of other proxy settings.
Troubleshooting
Localhost access
If a proxy is applied to the session, but you need access to a locally running server, use the loopback query parameter. This ensures that localhost traffic is redirected to the emulator, allowing seamless interaction with your local server.
Last updated
