**Describe the bug**
A clear and concise description of what the bug is.
I have a working configuration with Mosquitto + a reverse proxy and I would replace it with nanomq.
My aim is forward the websocket to a sub path of ngnix
I configured nanomq in this way:

# MQTT listener
listeners.tcp = {
  bind = "0.0.0.0:1883"     # The listener binds to all network interfaces on port 1883
}

# WebSocket listener
listeners.ws {
  bind = "0.0.0.0:8000"			# Bind to all network interfaces on port 8083
}

# Log settings
log = {
  to = [file, console]                  # Destination of the logs
  level = "warn"                        # Log level
  dir = "/tmp"                          # Directory for log files
  file = "nanomq.log"                   # Filename for the log file
  rotation = {
    size = "10MB"                       # Maximum size of each log file
    count = 5                           # Maximum rotation count of log files
  }
}

# Allow anonymous connections
auth {
	allow_anonymous = true # Allow clients to connect without providing username/password
}

And the ngnix: 

    location /mqtt
    {
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";
        proxy_set_header Host $host;

        proxy_pass http://localbroker:8000;
    }

How said before, the ngnix configuration works fine for a similar configuration with Mosquitto, but not for nanoMQ. I tried to use directly ws without ngnix and works fine.

**Expected behavior**
A clear and concise description of what you expected to happen.

Correct forward of mqtt websocket in subpath /mqtt

**Actual Behavior**
Describe what occurred.
The ngnix say they don't found the source and so doesn't forwrd connection.

**To Reproduce**
If possible include actual reproduction test code here.
Minimal C test cases are perferred.

**Environment Details**
 - NanoMQ version latest docker
 - Operating system and version Linux ubuntu 22.04
 - Compiler and language used N.A
 - testing scenario

**Client SDK**
If possible include the mqtt sdk you used to connect to nanomq
Minimal C test cases are perferred.
N.A

**Additional context**
Add any other context about the problem here.

Issue using nanoMQ behind reverse proxy ngnix
This is a GitHub Issue
repo:nanomq
owner:emqx
Title : Issue using nanoMQ behind reverse proxy ngnix
Issue date:

--- start body ---
**Describe the bug**
A clear and concise description of what the bug is.
I have a working configuration with Mosquitto + a reverse proxy and I would replace it with nanomq.
My aim is forward the websocket to a sub path of ngnix
I configured nanomq in this way:

# MQTT listener
listeners.tcp = {
  bind = "0.0.0.0:1883"     # The listener binds to all network interfaces on port 1883
}

# WebSocket listener
listeners.ws {
  bind = "0.0.0.0:8000"			# Bind to all network interfaces on port 8083
}

# Log settings
log = {
  to = [file, console]                  # Destination of the logs
  level = "warn"                        # Log level
  dir = "/tmp"                          # Directory for log files
  file = "nanomq.log"                   # Filename for the log file
  rotation = {
    size = "10MB"                       # Maximum size of each log file
    count = 5                           # Maximum rotation count of log files
  }
}

# Allow anonymous connections
auth {
	allow_anonymous = true # Allow clients to connect without providing username/password
}

And the ngnix: 

    location /mqtt
    {
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";
        proxy_set_header Host $host;

        proxy_pass http://localbroker:8000;
    }

How said before, the ngnix configuration works fine for a similar configuration with Mosquitto, but not for nanoMQ. I tried to use directly ws without ngnix and works fine.

**Expected behavior**
A clear and concise description of what you expected to happen.

Correct forward of mqtt websocket in subpath /mqtt

**Actual Behavior**
Describe what occurred.
The ngnix say they don't found the source and so doesn't forwrd connection.

**To Reproduce**
If possible include actual reproduction test code here.
Minimal C test cases are perferred.

**Environment Details**
 - NanoMQ version latest docker
 - Operating system and version Linux ubuntu 22.04
 - Compiler and language used N.A
 - testing scenario

**Client SDK**
If possible include the mqtt sdk you used to connect to nanomq
Minimal C test cases are perferred.
N.A

**Additional context**
Add any other context about the problem here.

--- end body ---
