Server Routing based on the `Host` header

Can you please add server routing based on the Host header?

It is very helpful in terms of routing to custom outbounds using only a single port and a single inbound.

Example:

Client 1

{
  "outbounds": [
    {
      "tag": "proxy",
      "type": "trojan",
      "server": "x.x.x.x",
      "server_port": 443,
      "password": "xxx",
      "tls": {
        "enabled": true,
        "server_name": "speedtest.com",
        "reality": {
          "enabled": true,
          "public_key": "xxx",
          "short_id": "xxx"
        },
        "utls": {
          "enabled": true,
          "fingerprint": "firefox"
        }
      },
      "transport": {
        "type": "httpupgrade",
        "host": "cdn-us.domain.com" <--------------1-----------------
      }
    }
  ]
}

Client 2

{
  "outbounds": [
    {
      "tag": "proxy",
      "type": "trojan",
      "server": "x.x.x.x",
      "server_port": 443,
      "password": "xxx",
      "tls": {
        "enabled": true,
        "server_name": "speedtest.com",
        "reality": {
          "enabled": true,
          "public_key": "xxx",
          "short_id": "xxx"
        },
        "utls": {
          "enabled": true,
          "fingerprint": "firefox"
        }
      },
      "transport": {
        "type": "httpupgrade",
        "host": "cdn-de.domain.com" <--------------2-----------------
      }
    }
  ]
}

Server Config

{
  "inbounds": [
    {
      "type": "trojan",
      "tag": "trojan-in",
      "listen": "0.0.0.0",
      "listen_port": 443,
      "users": [
        {
          "name": "user1@test",
          "password": "xxx"
        }
      ],
      "tls": {
        "enabled": true,
        "server_name": "speedtest.com",
        "reality": {
          "enabled": true,
          "handshake": {
            "server": "speedtest.com",
            "server_port": 443
          },
          "private_key": "xxx",
          "short_id": "xxx"
        }
      },
      "transport": {
        "type": "httpupgrade",
        "host": [
          "cdn-us.domain.com", <--------------1----------------
          "cdn-de.domain.com" <--------------2----------------
        ]
      }
    }
  ],
  "outbounds": [
    {
      "type": "direct",
      "tag": "direct"
    },
    {
      "tag": "cdn-us",
      "type": "socks",
      "server": "x.x.x.x",
      "server_port": 1080,
      "version": "5"
    },
    {
      "tag": "cdn-de",
      "type": "socks",
      "server": "y.y.y.y",
      "server_port": 1080,
      "version": "5"
    }
  ],
  "route": {
    "rules": [
      {
        "action": "sniff",
        "timeout": "5ms"
      },
      {
        "action": "hijack-dns",
        "protocol": "dns"
      },
      {
        "action": "resolve",
        "strategy": "ipv4_only"
      },
      {
        "host": "cdn-us.domain.com", <--------------1----------------
        "action": "route",
        "outbound": "cdn-us"
      },
      {
        "host": "cdn-de.domain.com", <--------------2----------------
        "action": "route",
        "outbound": "cdn-de"
      }
    ]
  }
}

Start by tracing how the server transport's HTTPUpgrade host values and route rules are parsed and applied. Compare the two client host values with the server configuration; done means a single inbound can distinguish those hosts and route each to its corresponding outbound.