
New: Expose GUI when creating tunnels through config using —gui flag.
Fix: Invalid host header when using custom wildcard domain.
Fix: LocalXpose process will exit automatically when all tunnels are closed.
Fix: —baisc-auth typo in command line.
Improve: Enhance tunnels and endpoints tables in the dashboard.


<ul>
<li>New: Expose GUI when creating tunnels through config using <code>—gui</code> flag.</li>
<li>Fix: Invalid host header when using custom wildcard domain.</li>
<li>Fix: LocalXpose process will exit automatically when all tunnels are closed.</li>
<li>Fix: <code>—baisc-auth</code> typo in command line.</li>
<li>Improve: Enhance tunnels and endpoints tables in the dashboard.</li>
</ul>

New Feature

Bug Fixes

Improvements

v23.11.1

Completed

[Describe the bug]When starting HTTP tunnel with a reserved custom wildcard domain like <code>*.dev.example.com</code>, LocalXpose client forwards non-TLS traffic to my <a target="_blank" rel="noopener noreferrer nofollow" href="http://localhost">localhost</a> service with invalid host header.[Steps To Reproduce]<ol>
<li>Start a tunnel like <code>loclx tunnel http —reserved-domain “*.dev.example.com“ —to localhost:80</code></li>
<li>Start a dummy server in <a target="_blank" rel="noopener noreferrer nofollow" href="http://localhost">localhost</a> like <code>nc -l 80 -vv</code></li>
<li>Create a request to the tunnel address like <code>curl http://hello.dev.example.com</code>.</li>
<li>See the dummy server logs and you will find the <code>Host: *.dev.example.com</code></li>
</ol>[Expected Behaviour]Host header should be the requested domain address, in the previous example should be <code>hello.dev.example.com</code>.

[Describe the bug]When starting HTTP tunnel with a reserved custom wildcard domain like *.dev.example.com, LocalXpose client forwards non-TLS traffic to my localhost service with invalid host header.[Steps To Reproduce]
Start a tunnel like loclx tunnel http —reserved-domain “*.dev.example.com“ —to localhost:80
Start a dummy server in localhost like nc -l 80 -vv
Create a request to the tunnel address like curl http://hello.dev.example.com.
See the dummy server logs and you will find the Host: *.dev.example.com
[Expected Behaviour]Host header should be the requested domain address, in the...

Someone

**[Describe the bug]**

When starting HTTP tunnel with a reserved custom wildcard domain like `*.dev.example.com`, LocalXpose client forwards non-TLS traffic to my [localhost](http://localhost) service with invalid host header.

**[Steps To Reproduce]**

1. Start a tunnel like `loclx tunnel http —reserved-domain “*.dev.example.com“ —to localhost:80`

2. Start a dummy server in [localhost](http://localhost) like `nc -l 80 -vv`

3. Create a request to the tunnel address like `curl http://hello.dev.example.com`.

4. See the dummy server logs and you will find the `Host: *.dev.example.com`

**[Expected Behaviour]**

Host header should be the requested domain address, in the previous example should be `hello.dev.example.com`.



Invalid host header when using wildcard domain

Subscribe to post