Max/XTLS_Xray-docs-next
1
0
Fork 0
mirror of https://github.com/XTLS/Xray-docs-next.git synced 2026-10-11 00:38:18 +03:00
Code Issues Packages Projects Releases Wiki Activity

TLS: Remove ECH Force Query

Browse Source 
Sync RU doc
This commit is contained in:
Fangliding
2026-04-29 19:24:40 +08:00
parent 122a055eb4
commit a1f2913bad
3 changed files with 11 additions and 44 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/en/config/transport.md
-13
View File
@@ -132,7 +132,6 @@ FinalMask configuration, used for general traffic obfuscation.
"masterKeyLog": "",
"echServerKeys": "",
"echConfigList": "",
"echForceQuery": "",
"echSockopt": {}
}
```
@@ -296,18 +295,6 @@ The basic format is `"udp://1.1.1.1"`, indicating querying from UDP DNS 1.1.1.1.
Specifically, you can use a designated domain for querying ECHConfig, in the format `"example.com+https://1.1.1.1/dns-query"`. In this way, Xray will force the use of the ECHConfig in the DNS record of `example.com` for connection. This is useful if you want to get ECHConfig from DNS but don't want to expose yourself querying the HTTPS record of this domain or publishing HTTPS records under this domain.
> `echForceQuery` : string
Controls the strategy when using DNS to query ECH Config. Options: `none` (default), `half`, `full`.
`none`: Query once. If a valid ECH Config is not obtained, it will query again after five minutes. If the query fails, **ECH will not be used**.
`half`: Query once. If failed, attempts to query on every request. If the query fails, **ECH will not be used**. If the query succeeds and gets a response but does not contain ECH Config, **ECH will not be used** either, and it will not query again within five minutes.
`full`: Query once. Forcibly requires a valid ECH Config to connect successfully; otherwise, the connection fails. Recommended if you definitely want to use ECH. The first two simulate fallback behavior to ensure availability but may lead to plaintext SNI being sent.
Regardless of query success or failure, only the first connection will block waiting for the query response result; subsequent updates will not block connections.
> `echSockopt` : [SockoptObject](#sockoptobject)
Adjusts the underlying socket options of the connection used when querying ECH records using DNS.