Skip to content
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 mode] alpn in client-hello make it's v2ray #1926

Closed
liudongmiao opened this issue Aug 22, 2022 · 6 comments
Closed

[websocket mode] alpn in client-hello make it's v2ray #1926

liudongmiao opened this issue Aug 22, 2022 · 6 comments
Labels
bug Something isn't working Stale

Comments

@liudongmiao
Copy link

liudongmiao commented Aug 22, 2022

type alpn
go-https (net/http) h2, http/1.1
v2ray-core http/1.1
go-websocket (github.com/gorilla/websocket) N/A

Referer: 8e791e9#diff-98874970fe9e833c1469702de67b4a0d1c731059ad04a00a349093f52f141f31R48

And for web browsers:

scheme alpn
https h2, http/1.1
wss http/1.1

Please note, websocket over http2 is not supported.
IMO, v2ray-core should send h2, http/1.1 like go-https (net/http), however, this requires server (like nginx) turn off http2.

@liudongmiao liudongmiao changed the title alpn in client-hello make it's v2ray [websocket mode] alpn in client-hello make it's v2ray Aug 22, 2022
@liudongmiao
Copy link
Author

JA3 fingerprint: https://engineering.salesforce.com/tls-fingerprinting-with-ja3-and-ja3s-247362855967

@AkinoKaede AkinoKaede added the bug Something isn't working label Aug 23, 2022
@klzgrad
Copy link

klzgrad commented Oct 12, 2022

FYI: WebSocket over H2 is supported after Chrome 91. https://chromestatus.com/feature/6251293127475200

@liudongmiao
Copy link
Author

FYI: WebSocket over H2 is supported after Chrome 91. https://chromestatus.com/feature/6251293127475200

@klzgrad I have chedked it before, however there is no way to turn on. And from my case, browser always send http/1.1 for wss.

@klzgrad
Copy link

klzgrad commented Oct 14, 2022

@liudongmiao
Copy link
Author

@klzgrad Just use chrome with a wss://.... then use wireshark to dump the packets.

@github-actions
Copy link
Contributor

This issue is stale because it has been open 120 days with no activity. Remove stale label or comment or this will be closed in 5 days

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Stale
Projects
None yet
Development

No branches or pull requests

3 participants