Mailing-List: contact dev-help@hc.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "HttpComponents Project" <dev@hc.apache.org>
Date: Fri, 14 Mar 2014 12:17:46 +0000 (UTC)
From: "Nathan Bryant (JIRA)" <jira@apache.org>
To: dev@hc.apache.org
Message-ID: <JIRA.12701456.1394799357588.68900.1394799466192@arcas>
In-Reply-To: <JIRA.12701456.1394799357588@arcas>
References: <JIRA.12701456.1394799357588@arcas>
Subject: [jira] [Updated] (HTTPCLIENT-1482) ability to expect-continue only
 if potentially stale
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Nathan Bryant updated HTTPCLIENT-1482:
--------------------------------------

    Summary: ability to expect-continue only if potentially stale  (was: ablity to expect-continue only if potentially stale)

> 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
>            Reporter: Nathan Bryant
>            Priority: Minor
>
> 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
(v6.2#6252)

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