Package org.eclipse.jetty.client
package org.eclipse.jetty.client
-
ClassDescription
Authenticationrepresents a mechanism to authenticate requests for protected resources.Structure holding information about theWWW-Authenticate(orProxy-Authenticate) header.Authentication.Resultholds the information needed to authenticate aRequestviaAuthentication.Result.apply(Request).A store forAuthentications andAuthentication.Results.Implementation of the HTTP "Basic" authentication defined in RFC 2617.Basic authentication result.Implementation ofResponse.Listenerthat buffers the content up to a maximum length specified to the constructors.ARequest.ContentforByteBuffers.ARequest.Contentfor byte arrays.ABufferingResponseListenerthat sends aRequestand returns aCompletableFuturethat is completed whenCompletableResponseListener.onComplete(Result)is called.Connectionrepresent a connection to aDestinationand allow applications to send requests viaConnection.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.ContentDecoderdecodes content bytes of a response.Factory forContentDecoders; subclasses must implementContentDecoder.Factory.newContentDecoder().A specializedResponsethat can hold a limited content in memory.ARequest.Contentthat wraps aContent.Source.A protocol handler that handles the 100 response code.ADestinationrepresents the receiver of HTTP requests, and it is identified by anOrigin.Implementation of the HTTP "Digest" authentication defined in RFC 2617.A protocol handler that handles the 103 response code.ARequest.Contentfor form uploads with the "application/x-www-form-urlencoded" content type.Deprecated.ContentDecoderfor the "gzip" encoding.SpecializedContentDecoder.Factoryfor the "gzip" encoding.HttpClient provides an efficient, asynchronous, non-blocking implementation to perform HTTP requests to a server through a simple API that offers also blocking semantic.HttpClientTransportrepresents what transport implementations should provide in order to plug-in a different transport forHttpClient.Client-side proxy configuration for HTTP proxying, as specified by RFC 9110.Utility class that handles HTTP redirects.HttpUpgrader prepares a HTTP request to upgrade from one protocol to another, and implements the upgrade mechanism.A factory forHttpUpgraders.ARequest.Contentthat produces content from anInputStream.Implementation ofResponse.Listenerthat produces anInputStreamthat allows applications to read the response content.ARequest.Contentfor 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.ARequest.Contentthat provides content asynchronously through anOutputStreamsimilar toAsyncRequestContent.ARequest.Contentfor files using JDK 7'sjava.nio.fileAPIs.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 forProtocolHandlers accessible fromHttpClient.getProtocolHandlers().A protocol handler that handles the 401 response code in association with theProxy-Authenticateheader.The configuration of the forward proxies to use withHttpClient.ClientConnectionFactory for the PROXY protocol.A ClientConnectionFactory for the PROXY protocol version 1.PROXY protocol version 1 metadata holder to be used in conjunction withRequest.tag(Object).A ClientConnectionFactory for the PROXY protocol version 2.PROXY protocol version 2 metadata holder to be used in conjunction withRequest.tag(Object).AConnectionPoolthat provides connections randomly among the ones that are available.A protocol handler that handles redirect status codes 301, 302, 303, 307 and 308.Requestrepresents 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.Responserepresents 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 listenersListener for the response succeeded event.AConnectionPoolthat 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 forSocks5.Authentications.The implementation of theNO AUTHauthentication method defined in RFC 1928.The implementation of theUSERNAME/PASSWORDauthentication 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.ARequest.Contentfor 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 theWWW-Authenticateheader.
CompletableResponseListenerinstead