You can leverage these environment variables to define your proxy settings. If these proxy environment variables are set then the tunnel will automatically detect them. You can switch command-line flags through an environment variable or .lt.yaml==$0 file with the LambdaTest tunnel. To configure the .lt.yaml, you can refer to the section Leverage .lt.yaml file of the documentation LambdaTest Tunnel For Corporate Firewalls/ Enterprise Restricted Environments.
Environment variables can be used in place of command-line flags. Each operating system has its compatibility in terms of environment variables. Command-line flags restrict environment variables from being bypassed. When available, the command-line flags always take priority.
Below is the following list of environment variables used by the LambdaTest Tunnel
|ENVIRONMENT VARIABLE||DESCRIPTION||OPERATING SYSTEM|
|LambdaTest tunnel uses the HTTP proxy ||Windows, Mac OS, Linux|
|LambdaTest tunnel uses the HTTPS proxy ||Windows, Mac OS, Linux|
|Comma separated list of hosts to bypass proxy when using tunnel. Wild cards is supported for sub-domains.||Windows, Mac OS, Linux|
LambdaTest Access Key
|Windows, Mac OS, Linux, FreeBSD|
That was all you need to know for LambdaTest tunnel proxies. In case you have any questions, feel free to share them with us. Our experts are available on 24/7 chat support. You can also drop us a mail at [email protected]. Happy testing! 🙂