[
https://issues.apache.org/jira/browse/HTTPCLIENT-1482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18030936#comment-18030936
]
Oleg Kalnichevski commented on HTTPCLIENT-1482:
-----------------------------------------------
[~abernal] I think implementation of this config policy was a mistake. The
feature was requested over ten years ago and since then better mechanisms of
dealing with stale connections and out of sequence responses have been created.
This config parameter is more confusing than helpful.
I suggest this change-set be backed out from 5.6.
Oleg
> 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]
