fix: keep isTLS field in keepalive when reset the request #876
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.
What type of PR is this?
fix
Check the PR title.
<type>(optional scope): <description>
.(Optional) Translate the PR title into Chinese.
长链接场景重置请求时保留,请求中和连接相关的字段(isTLS)
(Optional) More detail description for this PR(en: English/zh: Chinese).
en:
There is a special filed (isTLS) in the request, which is a link-related field, and its life cycle follows the link. Therefore, in the keepalive scenario, this field needs to be skipped when resetting the request, otherwise it will affect the scheme judgment of the subsequent request of the long link.
zh(optional):
请求里有个特殊filed(isTLS),它是一个链接相关字段,生命周期跟随链接,因此在长链接复用场景,重置请求的时候需要跳过该字段,否则影响长链接后续请求的scheme判断。
(Optional) Which issue(s) this PR fixes:
fixes #874
(Optional) The PR that updates user documentation: