The The SmartBear Secure Tunnel is available in form of a desktop application and command line utility. All they use similar options to specify the connection details.
The SmartBear Secure Tunnel supports the following connection types:
Most basic type of tunnel that works in most cases. It creates an encrypted tunnel that allows traffic and requests to be routed through the local network of your computer. This allows you to test sites that are only accessible through your local network or behind your firewall.
Select this mode if the tested local server is behind a “non-transparent” proxy on your side. This mode is useful for corporate environments that require proxies for HTTP/HTTPS traffic.
If you select this mode, you will need to specify the following settings:
The IP address of the proxy server in your network.
The proxy port number.
Local HTML files
Currently, BitBar doesn’t use them. You can see it in the SecureTunnel desktop app or the command-line utility. These are shared applications with other SmartBear products.
Bypass tunnel for public URLs
When the tunnel is up and running, it routes requests from the test device to the tested server app. Select this check box if you want to skip using the tunnel for requests that the tested client app sends to publicly available websites. This will generally speed up tests since many applications call publicly available resources.
If the tunnel is unable to resolve a URL publicly, it resolves it through the user computer.
Accept all SSL certificates
Select this check box so that the tunnel considers all security certificates as valid. This is useful for testing interim versions of websites and services which may have self-signed or invalid certificates.
Requirements and limitations
- As a tunnel creates a secure connection, outbound ssh requests travel on the port 443 to be encrypted. Please remember to allow SSL on crossbrowsertesting.com via your firewall.
- The Java tunnel options are deprecated and will not be supported shortly.