fix ws early data compatibility #585
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
鉴于大部分用户的能力，建议改成输入某个参数就为空，而不是使用 |
|
请问这两个 core 不填 header name ，单独填写 earlydata length 时的行为是怎样的？ |
两者默认都是在路径中发送，不使用header |
|
感谢指出 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
f53d0ab 之后，如果early_data_header_name没有被用户设置，将会被设置成xray默认的Sec-WebSocket-Protocol（实际上前面已经判断过xray的情况了），但这不是v2ray或sing-box的默认行为