Skip to content
This repository has been archived by the owner on Aug 18, 2021. It is now read-only.

to be compatible with "peer" sni field #14

Closed
DuckSoft opened this issue Jul 30, 2020 · 3 comments
Closed

to be compatible with "peer" sni field #14

DuckSoft opened this issue Jul 30, 2020 · 3 comments

Comments

@DuckSoft
Copy link
Member

DuckSoft commented Jul 30, 2020

Personally I think it totally nonsense to use peer for SNI.
However, it may be necessary to support the field peer, since it's used by Shadowrocket.

Users are innocent. Just don't build another wall.

Ref: Qv2ray/Qv2ray#844

@ghost
Copy link

ghost commented Jul 30, 2020

@DuckSoft Peer is not a standard. That's a shit name.
Ignored, anyone who wants it supported may open a PR.

@ghost
Copy link

ghost commented Jul 30, 2020

@DuckSoft Users are innocent but the shit standard isn''t.

@ghost ghost closed this as completed Aug 2, 2020
@ghost ghost pinned this issue Aug 13, 2020
@DuckSoft
Copy link
Member Author

v2board/v2board#295

This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

No branches or pull requests

1 participant