id | title | hide_title | sidebar_label | description | keywords | image | url | site_name | slug | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
tunnel-allowHost-wildcard-support |
Support for Wildcard in --allowHosts Flag |
false |
Wildcard Support |
Now you can use wildcard values for the -allow-Host flag for setting up the tunnel at lambdatest. |
|
/assets/images/og-images/docker-tunnel.png |
LambdaTest |
tunnel-allowHost-wildcard-support/ |
LambdaTest Tunnel now supports wildcard entries in the --allowHosts
flag. This enhancement allows users to specify patterns for hostnames instead of listing each subdomain separately, making it more flexible and efficient.
The --allowHosts
flag enables users to define which domains should be routed through the LambdaTest Tunnel while allowing other traffic to bypass it. With the new wildcard support, you can match multiple subdomains easily.
Follow these guidelines when using wildcards in domain names:
- Do not include
http://
orhttps://
. - ✅ Example:
example.com
.
- Ensure that the list of domains is comma-separated with no spaces.
- ✅ Example:
example.com
,testsite.com
,anotherdomain.com
- Prefix the domain with a dot
(.)
to match all its subdomains. - Alternatively, you can use an asterisk
(*)
for the same effect. - ✅ Example:
".example.com"
or"*.example.com"
will matchsub.example.com
,api.example.com
,blog.example.com
, etc.
:::tip Note Enclose the argument in quotes to prevent shell expansion of the asterisk (*). :::
- Simplifies Configuration : No need to manually list each subdomain.
- Increased Flexibility : Easily manage multiple subdomains with a single entry.
- Better Performance : Reduces manual domain management, improving efficiency.