purgatory/Xray-docs-next
1
0
Fork 0
mirror of https://github.com/XTLS/Xray-docs-next.git synced 2025-04-05 14:23:34 +03:00
Code Issues Projects Releases Packages Wiki Activity

prettiered

Browse source
This commit is contained in:
picklefan 2023-04-01 02:46:15 -07:00
parent c6767537a1
commit 19364280e9
3 changed files with 6 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
docs/en/config/features/browser_dialer.md
View file

@ -23,7 +23,7 @@ According to the browser's needs, the early data mechanism has been adjusted as
- The server response header will contain the requested `Sec-WebSocket-Protocol`, which also initially obfuscates the length characteristic of the WSS handshake response.
- The encoding used for early data for browsers is `base64.RawURLEncoding` instead of `StdEncoding`, and the server has made it compatible.
- In addition, due to [Xray-core#375](https://github.com/XTLS/Xray-core/pull/375) recommendations for `?ed=2048`, this PR also increased server `MaxHeaderBytes` by 4096. ~~(Although it seems like it would work without modification.)~~
- In addition, due to [Xray-core#375](https://github.com/XTLS/Xray-core/pull/375) recommendations for `?ed=2048`, this PR also increased server `MaxHeaderBytes` by 4096. ~~(Although it seems like it would work without modification.)~~
## Configuration <Badge text="v1.4.1" type="warning"/>
@ -33,4 +33,4 @@ This is an exploratory process, and the configuration method used when both side
- If browser traffic will also pass through Xray-core, be sure to set this domain name as a direct connection, otherwise it will cause traffic looping.
- Set the environment variable to specify the address port to listen on, such as `XRAY_BROWSER_DIALER = 127.0.0.1:8080`.
- First run Xray-core, then use any browser to access the specified address port, and you can also check `Console` and Network with `F12`.
- The browser will limit the number of WebSocket connections, so it is recommended to enable `Mux.Cool`.
- The browser will limit the number of WebSocket connections, so it is recommended to enable `Mux.Cool`.

3
docs/en/config/features/fallback.md
View file

@ -74,9 +74,10 @@ Note: **The inbound where fallbacks is located must be TCP+TLS**. This is for ro
Determines the destination of decrypted TLS TCP traffic, which currently supports two types of addresses: (this field is required, otherwise it cannot be started)
1. TCP, in the format of `"addr:port"`, where addr supports IPv4, domain names, and IPv6. If a domain name is entered, a direct TCP connection will be made (rather than using the built-in DNS resolver).
2. Unix domain socket, in the format of an absolute path, such as `"/dev/shm/domain.socket"`, which can be prefixed with `@` to represent [abstract](https://www.man7.org/linux/man-pages/man7/unix.7.html), and `@@` to represent padded abstract.
2. Unix domain socket, in the format of an absolute path, such as `"/dev/shm/domain.socket"`, which can be prefixed with `@` to represent [abstract](https://www.man7.org/linux/man-pages/man7/unix.7.html), and `@@` to represent padded abstract.
If only the port is specified, both numbers and strings are accepted, such as `80` or `"80"`. This usually points to a plaintext HTTP service (and the addr will be filled in as `"127.0.0.1"`).
> `xver`: number
Sends the [PROXY protocol](https://www.haproxy.org/download/2.2/doc/proxy-protocol.txt) protocol, which is used to transmit the real source IP and port of the request. The version can be set to `1` or `2`, with a default value of `0`, which means no PROXY protocol is sent. Version `1` is recommended if needed.

4
docs/en/config/features/multiple.md
View file

@ -82,7 +82,7 @@ In the JSON configuration, `inbounds` and `outbounds` are array structures with
- For `inbounds`, add it to the end (the order of elements in `inbounds` is irrelevant).
- For `outbounds`, add it to the beginning (the default first-choice outbound). However, if the filename contains "tail" (case-insensitive), add it to the end.
With multiple configurations, it is easy to add inbound for different protocols to the original configuration without modifying the original configuration.
With multiple configurations, it is easy to add inbound for different protocols to the original configuration without modifying the original configuration.
The following example is not a valid configuration but is provided to demonstrate the above rules.
@ -165,7 +165,7 @@ for BASE in 00_log 01_api 02_dns 03_routing 04_policy 05_inbounds 06_outbounds 0
├── 01_api.json
├── 02_dns.json
├── 03_routing.json
├── 04_policy.json
├── 04_policy.json
├── 05_inbounds.json
├── 06_outbounds.json
├── 07_transport.json