[
https://issues.apache.org/jira/browse/HTTPCLIENT-1482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18031386#comment-18031386
]
ASF subversion and git services commented on HTTPCLIENT-1482:
-------------------------------------------------------------
Commit c8b60aedc68b775ccb1efdac72f84d4295afd663 in httpcomponents-client's
branch refs/heads/master from Oleg Kalnichevski
[ https://gitbox.apache.org/repos/asf?p=httpcomponents-client.git;h=c8b60aedc ]
Revert "HTTPCLIENT-1482: added ExpectContinueTrigger, extended RequestConfig,
and modified RequestExpectContinue so that Expect: 100-continue is emitted only
when the underlying connection has already processed at least one request;
default behaviour (ALWAYS) preserved, API remains binary-compatible. (#683)"
This reverts commit 97fd9319
> ability to expect-continue only if potentially stale
> ----------------------------------------------------
>
> Key: HTTPCLIENT-1482
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1482
> Project: HttpComponents HttpClient
> Issue Type: Wish
> Components: HttpClient (classic)
> Reporter: Nathan Bryant
> Priority: Minor
> Fix For: 5.6-alpha1
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> If the stale check fails, non-idempotent queries such as POST can return a
> "no response from server" error to the application stack, resulting in
> ambiguity as to whether the request was received and acted on in some fashion
> by the host, possibly resulting in a server-side error.
> Might be nice as a RequestConfig option to be able to enable the
> expect-continue handshake only for cases where the connection was recycled
> from a pool.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
