-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Websocket Early Data and Browser forwarder Improvement #818
Conversation
browser forwarder config: set this at root configure document
|
websocket setting:
|
i do not liked on near changes that add new Object at root configuration: FakeDNSObject and BrowserForwarderObject, as this break the past infrastructure of v2ray root configuration: log, dns, inbounds, outbounds, routing, etc. could you move these? |
I have to say that, FakeDNS, BrowserForwarder are top level component of V2Ray instance, and it is most trivial to put them in the root document. What kind of change would you suggest to make? |
@xiaokangwang like this. {
"common": {
"fakedns": {},
"browserforwarder": {}
}
} |
Still waiting for opinion from @kslr |
It seems there is an issue about safety: https://github.com/v2fly/v2ray-core/pull/818/checks?check_run_id=2210672378 |
I believe there is a check below that discard any unrecognized user supplied value. |
This is a improvement of Web-Sockets transport that allow WebSocket connection to send early data in path, which reduce the WebSocket's connection establishment time, and browser forward, which will use any browser's WebSocket framework to automatically relay the traffic, which will have the same TLS fingerprint as browser initialized WSS traffic.
@RPRX 已经要求我不能早于其发布此改进。