XHTTP + Reality 在 mode=auto 时失败（unexpected response version 88），mode=stream-one 正常

[lyd123qw2008]

完整性要求

• 我读完了 issue 模板中的所有注释，确保填写符合要求。
• 我保证阅读了文档，了解所有我编写的配置文件项的含义，而不是大量堆砌看似有用的选项或默认值。
• 我提供了完整的配置文件和日志，而不是出于自己的判断只给出截取的部分。
• 我搜索了 issues, 没有发现已提出的类似问题。
• 问题在 Release 最新的版本上可以成功复现

描述

Xray-core 26.1.31（Windows 客户端）在 VLESS + Reality + XHTTP 的场景下，xhttpSettings.mode=auto 无法连接，报错 proxy/vless/encoding: unexpected response version. Expecting 0 but actually 88。
将 xhttpSettings.mode 显式改为 stream-one 后即恢复正常。
这是从旧版本升级到 26.1.31 后出现的问题（之前 auto 可用）。
排查到 Xray 在 XHTTP dial 时对 auto 的处理可能与 sessionId 生成逻辑不一致：auto 在 Reality 下应等价 stream-one，但仍生成 sessionId，导致 server 侧走了非 stream-one 的处理路径。

相关源码（供参考）：

• transport/internet/splithttp/dialer.go：sessionId 生成发生在 auto -> stream-one 的解析之前
• transport/internet/splithttp/hub.go：带 sessionId 的请求会走 stream-up / packet-up 分支

重现方式

1. 服务端使用下方服务端配置启动 Xray-core（Linux）。
2. 客户端使用下方客户端配置启动 Xray-core（Windows）。
3. 访问任意 https 网站（例如 https://www.google.com）。
4. 观察客户端日志，出现 unexpected response version. Expecting 0 but actually 88。
5. 将客户端 xhttpSettings.mode 改为 stream-one，重启后连接恢复正常。

客户端配置

Details

  {
    "log": { "loglevel": "debug", "dnsLog": true },
    "inbounds": [
      {
        "tag": "socks",
        "port": 10808,
        "listen": "127.0.0.1",
        "protocol": "mixed",
        "settings": { "auth": "noauth", "udp": true }
      }
    ],
    "outbounds": [
      {
        "tag": "proxy",
        "protocol": "vless",
        "settings": {
          "vnext": [
            {
              "address": "SERVER_IP",
              "port": 14183,
              "users": [
                {
                  "id": "UUID",
                  "encryption": "none"
                }
              ]
            }
          ]
        },
        "streamSettings": {
          "network": "xhttp",
          "security": "reality",
          "xhttpSettings": {
            "path": "/tcobxHTTP",
            "host": "www.suny.edu",
            "mode": "auto"
          },
          "realitySettings": {
            "serverName": "www.suny.edu",
            "fingerprint": "chrome",
            "publicKey": "PUBLIC_KEY",
            "shortId": "SHORT_ID",
            "spiderX": ""
          }
        }
      },
      { "tag": "direct", "protocol": "freedom" }
    ]
  }
  

服务端配置

Details

  {
    "log": { "loglevel": "debug", "dnsLog": true },
    "inbounds": [
      {
        "listen": "0.0.0.0",
        "port": 14183,
        "protocol": "vless",
        "settings": {
          "clients": [
            {
              "id": "UUID",
              "email": "test@test",
              "encryption": "none"
            }
          ],
          "decryption": "none"
        },
        "streamSettings": {
          "network": "xhttp",
          "security": "reality",
          "xhttpSettings": {
            "path": "/tcobxHTTP"
          },
          "realitySettings": {
            "show": false,
            "dest": "www.suny.edu:443",
            "serverNames": ["www.suny.edu"],
            "privateKey": "PRIVATE_KEY",
            "shortIds": ["SHORT_ID"]
          }
        }
      }
    ],
    "outbounds": [
      { "protocol": "freedom", "tag": "direct" }
    ]
  }
  

客户端日志

Details

  Xray 26.1.31 (windows/amd64)
  ...
  [Info] transport/internet/splithttp: XHTTP is dialing to tcp:SERVER_IP:14183, mode auto, HTTP version 2, host www.suny.edu
  [Info] proxy/vless/outbound: tunneling request to tcp:www.google.com:443 via SERVER_IP:14183
  [Info] app/proxyman/outbound: failed to process outbound traffic > proxy/vless/outbound: connection ends > proxy/vless/outbound: failed to decode response header > proxy/vless/encoding: unexpected
  response version. Expecting 0 but actually 88
  

服务端日志

Details

  无
  

[RPRX]

#5633 (comment)

@paqx

[RPRX]

遇到问题后自行控制变量进行测试，然后看源码找到了 bug 所在并反馈，这才是高质量 issue，必须点个赞，送你上电视

[paqx]

@lyd123qw2008

Thanks for the detailed report. I had already set up a similar configuration and got the same error. I am currently trying to find the exact commit that introduced the issue. I hope I will soon have a fix.

[paqx]

Yes, it's definitely related to my changes. I am on it.

[RPRX]

@paqx 这个应该很好修吧，群友在催进度

[paqx]

@RPRX

It wasn't very easy for me, but I have finally finished.

I tested different configurations:

1. XHTTP (mode=auto)+REALITY
2. XHTTP (mode=packet-up)+REALITY
3. XHTTP (mode=stream-one)+REALITY
4. XHTTP (mode=stream-up)+REALITY
5. XHTTP (mode="")+REALITY
6. XHTTP (mode=auto)
7. XHTTP (mode=packet-up)
8. XHTTP (mode=stream-one)
9. XHTTP (mode=stream-up)
10. XHTTP (mode="")

Seems to work correctly.

[regenerativeFox]

Thanks for posting/fixing the issue and maintaining this great project. Could you please temporarily remove release/image 26.1.31 from xray-install and packages (docker registry) since it breaks backward compatibility and thus users get buggy updates as of now? Got stuck checking out my config since yesterday xD

[EvgenyAfanasev]

Thank you so much for this issue. It's save my debug time !

[wy15]

xhttp+tls开启Browser Dialer，26.1.23可以正常使用。26.2.6报错app/proxyman/outbound: app/proxyman/outbound: failed to process outbound traffic > proxy/vless/outbound: ML-KEM-768 handshake failed > websocket: close 1005 (no status)