/** A handler for determining if an HTTP response represents an authentication challenge that was sent back to the client as a result of authentication failure.
Represents a controller that dynamically adjusts the size of an available connection pool based on feedback from using the connections.
When managing a dynamic number of connections for a given route, this strategy assesses whether a given request execution outcome should result in a backoff signal or not, based on either examining the
This interface represents an abstract store for
Abstract credentials provider that maintains a collection of user credentials.
This interface represents only the most basic contract for HTTP request execution.
A handler for determining if an HttpRequest should be retried after a recoverable exception during execution.
A strategy for determining if an HTTP request should be redirected to a new location in response to an HTTP response received from the target server.
(4.3) No longer used
Handler that encapsulates the process of generating a response object from a
Strategy interface that allows API users to plug in their own logic to control whether or not a retry should automatically be done, how many times it should be retried and so on.
A handler for determining if the given execution context is user specific or not.
Signals a circular redirect
Signals an error in the HTTP protocol.
Signals a non 2xx HTTP response.
Signals failure to retry the request due to non-repeatable request entity.
Signals violation of HTTP specification caused by an invalid redirect
Copyright © 1999–2015 The Apache Software Foundation. All rights reserved.