Example usage for org.apache.http.impl.execchain ClientExecChain interface-usage

List of usage examples for org.apache.http.impl.execchain ClientExecChain interface-usage

Introduction

In this page you can find the example usage for org.apache.http.impl.execchain ClientExecChain interface-usage.

Usage

From source file org.callimachusproject.client.UnavailableRequestDirector.java

public class UnavailableRequestDirector implements ClientExecChain {

    @Override
    public CloseableHttpResponse execute(HttpRoute route, HttpRequestWrapper request,
            HttpClientContext clientContext, HttpExecutionAware execAware) throws IOException, HttpException {
        BasicHttpResponse _503 = new BasicHttpResponse(HttpVersion.HTTP_1_1, 503, "Service Disconnected");

From source file org.callimachusproject.client.AuthenticationClientExecChain.java

public class AuthenticationClientExecChain implements ClientExecChain {
    private final HttpAuthenticator authenticator;
    private final ClientExecChain delegate;

    public AuthenticationClientExecChain(ClientExecChain delegate) {
        this.authenticator = new HttpAuthenticator();

From source file org.apache.http.impl.execchain.ServiceUnavailableRetryExec.java

/**
 * Request executor in the request execution chain that is responsible
 * for making a decision whether a request that received a non-2xx response
 * from the target server should be re-executed.
 * <p/>
 * Further responsibilities such as communication with the opposite

From source file org.apache.http.impl.execchain.RetryExec.java

/**
 * Request executor in the request execution chain that is responsible
 * for making a decision whether a request failed due to an I/O error
 * should be re-executed.
 * <p/>
 * Further responsibilities such as communication with the opposite

From source file org.apache.http.impl.execchain.RedirectExec.java

/**
 * Request executor in the request execution chain that is responsible
 * for handling of request redirects.
 * <p/>
 * Further responsibilities such as communication with the opposite
 * endpoint is delegated to the next executor in the request execution

From source file org.apache.http.impl.execchain.ProtocolExec.java

/**
 * Request executor in the request execution chain that is responsible
 * for implementation of HTTP specification requirements.
 * Internally this executor relies on a {@link HttpProcessor} to populate
 * requisite HTTP request headers, process HTTP response headers and update
 * session state in {@link HttpClientContext}.

From source file org.apache.http.impl.execchain.MinimalClientExec.java

/**
 * Request executor that implements the most fundamental aspects of
 * the HTTP specification and the most straight-forward request / response
 * exchange with the target server. This executor does not support
 * execution via proxy and will make no attempts to retry the request
 * in case of a redirect, authentication challenge or I/O error.

From source file org.apache.http.impl.client.cache.CachingExec.java

/**
 * Request executor in the request execution chain that is responsible for
 * transparent client-side caching. The current implementation is conditionally
 * compliant with HTTP/1.1 (meaning all the MUST and MUST NOTs are obeyed),
 * although quite a lot, though not all, of the SHOULDs and SHOULD NOTs
 * are obeyed too.

From source file org.apache.http.impl.execchain.MainClientExec.java

/**
 * The last request executor in the HTTP request execution chain
 * that is responsible for execution of request / response
 * exchanges with the opposite endpoint.
 * This executor will automatically retry the request in case
 * of an authentication challenge by an intermediate proxy or