[
https://issues.apache.org/jira/browse/HTTPCLIENT-1482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18031026#comment-18031026
]
Nathan Bryant commented on HTTPCLIENT-1482:
-------------------------------------------
I am the original requestor of this feature, more than 10 years ago.
Normally I would just request that [~olegk] should state what he means by
"better mechanisms" but he can't, because there aren't any. A TCP connection
can go stale for a variety of reasons (host died, or network connectivity
vanished) and in those situations, no notification is sent over the wire, so it
is not necessarily possible for the client to detect that until it sends a
probe.
> 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]
