[Backport] HTTP Expect: 100-continue
(#2037)
#2079
Merged
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.
Motivation:
Add support for
Expect: 100-continue
header to allow users deffersending request payload body until server signals that it's ready to
receive it.
Modification:
HttpObjectEncoder
,HttpObjectDecoder
,AbstractH2DuplexHandler
, their subclasses, andNettyHttpServer
tosupport new feature;
DefaultNettyConnection
: addContinueUserEvent
andCancelWriteUserEvent
;WriteStreamSubscriber
: addcontinueWriting()
andterminateSource()
to support continuation;WriteStreamSubscriber#channelWritable()
to makeinitialRequestN
if subscription was assigned while a channel was notwritable;
RequestResponseCloseHandler
andNonPipelinedCloseHandler
: fireOutboundDataEndEvent
only when it ends outbound data but not whenCancelWriteUserEvent
;HttpProtocolVersion
: implementComparable
interface to alloweasier version number comparison;
RetryingHttpRequesterFilter
: addretryExpectationFailed(boolean)
feature and public
ExpectationFailedException
;Expect: 100-continue
for http-api module;Result:
HTTP supports
Expect: 100-continue
feature on client and server sides.