XHTTP, WS, HU: Forbid "host" in headers, read serverName instead

[RPRX]

XHTTP, WS, HU 都有单独的 host 参数，没有必要允许 headers 里填 "host"，GUI 也不会把它填 headers 里，索性禁了

客户端未设置 host 时本来自动取 address，但若 TLS 或 REALITY 存在，显然取 address 不妥，应当取 serverName

客户端新的优先级顺序：host > serverName > address；服务端 host 是校验，没事别设，不会自动取 serverName

[Fangliding]

之前改成这样的原因是有伊朗人要填 hOsT (直接调go的函数修改host会全部统一成Host)

[RPRX]

之前改成这样的原因是有伊朗人要填 hOsT (直接调go的函数修改host会全部统一成Host)

这么久了伊朗 GFW 应该已经禁掉这歪门邪道了吧

[RPRX]

我看了下代码，除了 HTTPUpgrade，其它传输层对 headers 的处理都是调用 Add()（包括被删掉的 HTTP 传输层），也就是说以前最多是 HTTPUpgrade 能用 "hOst"，@Fangliding 确定伊朗人真的用到这个功能了吗

[Fangliding]

翻了一下加这个是要 Websocket→WebSocket 印象里好像确实有人要过hOsT但是找不到了 最开始说要这样设计应该是在这
#3191 (comment) 都是workaround 随便了 应该没人用反正

[RPRX]

最开始说要这样设计应该是在这 #3191 (comment)

这下回旋镖了 也不是

只是原本允许 headers 里写 "host"，它优先级肯定要高于 address 才合理，但现在我想读 serverName，headers 有点碍事了

[RPRX]

等下问题大条了，我发现原本 WebSocket 没有 host，所以 GUI 和很多人是写 headers 里的

[irgfw]

The reason for this change is that some Iranians want to fill in hOsT (directly calling the go function to modify the host will be unified into Host)

After such a long time, Iran's GFW should have banned this crooked practice.

Yes, it is indeed mostly blocked by now.

[hatinati2]

The reason for this change is that some Iranians want to fill in hOsT (directly calling the go function to modify the host will be unified into Host)

After such a long time, Iran's GFW should have banned this crooked practice.

Yes, it is indeed mostly blocked by now.

@RPRX @irgfw

Hello
If you use a proxy server or tunnel
The connection quality on Iran Telecom, Irancell, and Rightel without headers will be very bad and terrible, but by activating the header, the connection quality will improve significantly

On Irancell, if you do not have a header, WhatsApp will encounter many problems and will not even upload voice

You should think about both direct connection and tunneling

[mikeesierrah]

This PR fixes many of our problems and hassles well done!

[RPRX]

WebSocket 历史太久，先继续允许它 headers 填 host 吧，以后再禁，客户端需要及时采用新写法 @2dust

[RPRX]

@fodhelper 其实这种小把戏 Xray 加不加都行，反而不加的话它能活得更久

[irgfw]

The reason for this change is that some Iranians want to fill in hOsT (directly calling the go function to modify the host will be unified into Host)

After such a long time, Iran's GFW should have banned this crooked practice.

Yes, it is indeed mostly blocked by now.

@RPRX @irgfw

Hello If you use a proxy server or tunnel The connection quality on Iran Telecom, Irancell, and Rightel without headers will be very bad and terrible, but by activating the header, the connection quality will improve significantly

On Irancell, if you do not have a header, WhatsApp will encounter many problems and will not even upload voice

You should think about both direct connection and tunneling

This isn't the right place to discuss this, but the issues you mentioned typically arise when using VLESS without TLS, which is not recommended. If you prefer not to use TLS, consider switching to VMESS. However, be aware that recent updates to the IRGFW have started detecting VMESS and blocking destination IPs.

[RPRX]

还有“SNI 填 IP 以便不发 SNI”的用法需要注意，可能需要填 host 了，不过这用法基本上只有 REALITY，而 REALITY 不在意 host

[Fangliding]

搞这搞那的好处也没看到什么的 要不还是 蒜了

[RPRX]

说的是这个 PR 吗，凡是风扇反对的：

This PR fixes many of our problems and hassles well done!

[Fangliding]

说实话我都不知道这话里problems and hassles在说什么 哪怕有也不应该用many修饰 可能机翻的 pr desc 都没看懂只是纯粹夸夸而已

[RPRX]

因为 RAW、gRPC 补个 SNI 就行了，这三个还要补 host，忘了说，gRPC 默认把 SNI 当 authority，这个 PR 后行为一致

我加 read serverName 就是因为 https://t.me/projectXtls/510 我自己都忘了，还有我前天看到群里有个人也是加了 SNI 忘了 host

总之改之前最大的问题是反直觉，就像我说的：但若 TLS 或 REALITY 存在，显然取 address 不妥，应当取 serverName

[Fangliding]

那么多年过来一直都这样
说好听点 兼容老客户端 不耦合tls层和传输层(我最开始知道要写两个的时候是这么说服自己的) 非必要不动默认行为 不要轻易把本来严格的配置要求变得不严格
说难听点 祖宗之法不可变
嗯.....

[RPRX]

没啥不兼容的，这个 PR 前基本上填了 TLS SNI 的都要再填个 host 不然用不了，不受这个 PR 影响

这不是配置要求严不严格的问题，而是 host 为空时放着 SNI 不取而去取 address，很怪，跟 bug 一样，而这个 PR 算是 fix

祖宗之法不可变是什么玩意儿

[RPRX]

如果你指的是新节点分享给老客户端用不了，那他们要么多填个 host 要么要求升级客户端/内核，渐渐就好了，这是一个过程

[RPRX]

还有那个耦合，XHTTP 都用 TLS alpn 来决定 HTTP 版本了，也不反直觉，因为 IETF TLS 和内层 HTTP 设计上本来就是耦合的

[sssagsag]

XHTTP , WS, HU all have separate hostparameters, so there is no need to allow headers"host" to be filled in.The GUI will not fill it headersin., simply banned

If the client is not set , it will hostbe automatically selected address. However, if TLS or REALITY exists, it is obviously addressinappropriate to selectserverName

The new priority order of the client is: host> serverName> address; the server hostis a verification, don't set it if there is nothing to do, it will not be automatically selectedserverName

With these changes, many domain frontings will stop working. Why did you do this?

What will happen to the host now?

[mikeesierrah]

说的是这个 PR 吗，凡是风扇反对的：

This PR fixes many of our problems and hassles well done!

I was saying that from a GFW agents POV

[RPRX]

@sssagsag @mikeesierrah 你们什么理解能力啊

[sssagsag]

@sssagsag @mikeesierrah 你们什么理解能力啊

I don't know what's happening, let me give you an example, in the Cloudflare settings, the address points to an edge, sni, I use a fake domain that is a subset of the main domain, and the host domain points to my server, what changes are going to be made now?

[RPRX]

@sssagsag 这个 PR 仅在 host 为空时自动填上 serverName，不影响你所描述的配置，更不影响 domain fronting

@mikeesierrah 如果你的意思是这个 PR 删了 "hOst"，然而没删，因为 Xray 本来就没它，还有你们以为明文 HTTP 很好吗？