[ http://issues.apache.org/jira/browse/HTTPCORE-16?page=all ]
Oleg Kalnichevski resolved HTTPCORE-16.
---------------------------------------
Resolution: Invalid
There's not much we can do about it. HttpRequestExecutor changed a lot since
ALPHA2. One of those changes is that HttpRequestExecutor no longer attempts to
retry a failed request.
The trouble is that HttpRequestExecutor in some cases needs to re-open the
connection in order to be able to retry the request. The process of opening a
connection can be rather complex (if that connection must go via a proxy, for
instance). This poses a whole bunch of issues that cannot be adequately
resolved in HttpCore. What is proxy requires authentication? All connection
management code (including HTTP proxy support, HTTP authentication, request
retry support) belongs to HttpClient, not HttpCore.
Sorry about that.
Oleg
> When calling the retryRequest method in execute method in HttpRequestExecutor
> class, the third parameter is always null instead of passing the
> this.defaultContext parameter.
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: HTTPCORE-16
> URL: http://issues.apache.org/jira/browse/HTTPCORE-16
> Project: HttpComponents Core
> Issue Type: Bug
> Components: HttpCore
> Affects Versions: 4.0-alpha2
> Reporter: Flash Networks
> Attachments: HttpRequestExecutor.java
>
>
> When calling the retryRequest method in execute method in HttpRequestExecutor
> class,
> the third parameter is always null instead of passing the this.defaultContext
> parameter.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
