All Classes and Interfaces

Class
Description
 
 
 
 
 
 
Authentication represents a mechanism to authenticate requests for protected resources.
Structure holding information about the WWW-Authenticate (or Proxy-Authenticate) header.
Authentication.Result holds the information needed to authenticate a Request via Authentication.Result.apply(Request).
 
Implementation of the HTTP "Basic" authentication defined in RFC 2617.
Basic authentication result.
Implementation of Response.Listener that buffers the response content by copying it up to a maximum length specified to the constructors.
A Request.Content for byte arrays.
A RetainingResponseListener that sends a Request and returns a CompletableFuture that is completed when CompletableResponseListener.onComplete(Result) is called.
Connection represent a connection to a Destination and allow applications to send requests via Connection.send(Request, Response.CompleteListener).
Client-side connection pool abstraction.
Factory for ConnectionPool instances.
Marks a connection as supporting multiplexed requests.
Marks a connection as being usable for a maximum number of requests.
Groups abstractions related to response content decoding.
 
A factory for Content.Source that decode response content.
A specialized Response that can hold a limited content in memory.
A Request.Content that wraps a Content.Source.
A protocol handler that handles the 100 response code.
A Destination represents the receiver of HTTP requests, and it is identified by an Origin.
Implementation of the HTTP "Digest" authentication defined in RFC 2617.
 
A protocol handler that handles the 103 response code.
A Request.Content for form uploads with the "application/x-www-form-urlencoded" content type.
 
HttpClient provides an efficient, asynchronous, non-blocking implementation to perform HTTP requests to a server through a simple API that offers also blocking semantic.
Descendant beans of HttpClient that implement this interface are made aware of the HttpClient instance while it is starting.
 
Representation of the HTTP/1.1 application protocol used by HttpClientTransportDynamic.
 
HttpClientTransport represents what transport implementations should provide in order to plug in a different transport for HttpClient.
A HttpClientTransport that can dynamically switch among different application protocols.
 
 
 
 
 
Client-side proxy configuration for HTTP proxying, as specified by RFC 9110.
HttpReceiver provides the abstract code to implement the various steps of the receive of HTTP responses.
Utility class that handles HTTP redirects.
 
 
 
 
HttpSender abstracts the algorithm to send HTTP requests, so that subclasses only implement the transport-specific code to send requests over the wire, implementing HttpSender.sendHeaders(HttpExchange, ByteBuffer, boolean, Callback) and HttpSender.sendContent(HttpExchange, ByteBuffer, boolean, Callback).
HttpUpgrader prepares a HTTP request to upgrade from one protocol to another, and implements the upgrade mechanism.
A factory for HttpUpgraders.
 
A Request.Content that produces content from an InputStream.
Implementation of Response.Listener that produces an InputStream that allows applications to read the response content.
A Request.Content for form uploads with the "multipart/form-data" content type.
 
Class that groups the elements that uniquely identify a destination.
 
The representation of a network protocol.
A Request.Content that provides content asynchronously through an OutputStream similar to AsyncRequestContent.
A Request.Content for files using JDK 7's java.nio.file APIs.
Implementation of Response.ContentListener that saves the response content to a file Path, like curl <url> -o file.bin does.
 
A protocol handler that handles the 102 response code.
A protocol handler performs HTTP protocol operations on behalf of the application, typically like a browser would.
A container for ProtocolHandlers accessible from HttpClient.getProtocolHandlers().
A protocol handler that handles the 401 response code in association with the Proxy-Authenticate header.
The configuration of the forward proxies to use with HttpClient.
 
ClientConnectionFactory for the PROXY protocol.
 
A ClientConnectionFactory for the PROXY protocol version 1.
PROXY protocol version 1 metadata holder to be used in conjunction with Request.tag(Object).
A ClientConnectionFactory for the PROXY protocol version 2.
PROXY protocol version 2 metadata holder to be used in conjunction with Request.tag(Object).
 
 
 
 
A ConnectionPool that provides connections randomly among the ones that are available.
A protocol handler that handles redirect status codes 301, 302, 303, 307 and 308.
Request represents an HTTP request, and offers a fluent interface to customize various attributes such as the path, the headers, the content, etc.
Listener for the request begin event.
Listener for the request committed event.
A client-side representation of HTTP request content.
Listener for the request content event.
Listener for the request failed event.
Listener for the request headers event.
Listener for all request events.
Listener for the request queued event.
Common, empty, super-interface for request listeners.
Listener for the request succeeded event.
A specialized container for request listeners.
Response represents an HTTP response and offers methods to retrieve status code, HTTP version and headers.
Asynchronous listener for the response content events.
Listener for the response begin event.
Listener for the request and response completed event.
Synchronous listener for the response content events.
Asynchronous listener for the response content events.
Listener for the response failure event.
Listener for a response header event.
Listener for the response headers event.
Listener for all response events.
Common, empty, super-interface for response listeners
Listener for the response succeeded event.
A specialized container for response listeners.
The result of a request / response exchange, containing the Request, the Response and eventual failures of either.
Implementation of Response.Listener that retains the response content without copying it, up to a configurable number of bytes.
A ConnectionPool that attempts to provide connections using a round-robin algorithm.
 
Client-side proxy configuration for SOCKS4, a de-facto standard.
 
Helper class for SOCKS5 proxying.
A SOCKS5 authentication method.
A factory for Socks5.Authentications.
The implementation of the NO AUTH authentication method defined in RFC 1928.
The implementation of the USERNAME/PASSWORD authentication method defined in RFC 1929.
Client-side proxy configuration for SOCKS5, defined by RFC 1928.
Implementation of the SPNEGO (or "Negotiate") authentication defined in RFC 4559.
 
A Request.Content for strings.
A protocol handler that handles HTTP 101 responses.
A connection pool that validates connections before making them available for use.
A protocol handler that handles the 401 response code in association with the WWW-Authenticate header.