Package org.eclipse.jetty.client
package org.eclipse.jetty.client
-
ClassDescription
Authentication
represents a mechanism to authenticate requests for protected resources.Structure holding information about theWWW-Authenticate
(orProxy-Authenticate
) header.Authentication.Result
holds the information needed to authenticate aRequest
viaAuthentication.Result.apply(Request)
.A store forAuthentication
s andAuthentication.Result
s.Implementation of the HTTP "Basic" authentication defined in RFC 2617.Basic authentication result.Implementation ofResponse.Listener
that buffers the content up to a maximum length specified to the constructors.ARequest.Content
forByteBuffer
s.ARequest.Content
for byte arrays.ABufferingResponseListener
that sends aRequest
and returns aCompletableFuture
that is completed whenCompletableResponseListener.onComplete(Result)
is called.Connection
represent a connection to aDestination
and 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.ContentDecoder
decodes content bytes of a response.Factory forContentDecoder
s; subclasses must implementContentDecoder.Factory.newContentDecoder()
.A specializedResponse
that can hold a limited content in memory.ARequest.Content
that wraps aContent.Source
.A protocol handler that handles the 100 response code.ADestination
represents 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.Content
for form uploads with the "application/x-www-form-urlencoded" content type.Deprecated.ContentDecoder
for the "gzip" encoding.SpecializedContentDecoder.Factory
for 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.Descendant beans ofHttpClient
that implement this interface are made aware of theHttpClient
instance while it is starting.HttpClientTransport
represents 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 forHttpUpgrader
s.ARequest.Content
that produces content from anInputStream
.Implementation ofResponse.Listener
that produces anInputStream
that allows applications to read the response content.ARequest.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.ARequest.Content
that provides content asynchronously through anOutputStream
similar toAsyncRequestContent
.ARequest.Content
for files using JDK 7'sjava.nio.file
APIs.Implementation ofResponse.ContentListener
that saves the response content to a filePath
, likecurl <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 forProtocolHandler
s accessible fromHttpClient.getProtocolHandlers()
.A protocol handler that handles the 401 response code in association with theProxy-Authenticate
header.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)
.AConnectionPool
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 listenersListener for the response succeeded event.AConnectionPool
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 forSocks5.Authentication
s.The implementation of theNO AUTH
authentication method defined in RFC 1928.The implementation of theUSERNAME/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.ARequest.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 theWWW-Authenticate
header.
CompletableResponseListener
instead