hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oleg Kalnichevski (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HTTPCLIENT-1482) ability to expect-continue only if potentially stale
Date Fri, 14 Mar 2014 13:50:50 GMT

     [ https://issues.apache.org/jira/browse/HTTPCLIENT-1482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Oleg Kalnichevski updated HTTPCLIENT-1482:

      Component/s: HttpConn
    Fix Version/s: Future

This would require the connection manager to return additional details (new or re-used) upon
connection lease, which presently cannot be done without breaking connection management APIs.
It will have to wait until 5.0.


> 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: HttpConn
>            Reporter: Nathan Bryant
>            Priority: Minor
>             Fix For: Future
> 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
> 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

To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org

View raw message