Support 100-continue of server and remove expect header of request #2499
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 problem does this PR solve?
Issue Number:
Problem Summary:
客户端使用libcurl请求brpc http服务端,偶现耗时超过1秒的现象。经排查,发现是libcurl当使用Post或者Put方法,请求体超过一定大小(一般是1024字节)时,libcurl 自动添加“Expect: 100-continue”请求头,先发送header,等到服务端确认能接收body,收到服务端的100 continue response或者超过1秒,才发送body部分数据给服务端。
详细见libcurl Expect 100-continue 和rfc7231。
What is changed and the side effects?
Changed:
Side effects:
Performance effects(性能影响):
Breaking backward compatibility(向后兼容性):
Check List: