Representation of a HTTP message body
The release of resources must be idempotent, meaning that
be called after complete consumption of the body and it may also be called
Output pipe for writing http responses
Helper functions for the client
HTTP response received by the client
Response message. This have no meaning for the HTTP connection, its just for human enjoyment.
BodyReader used to consume the response body.
Provider of HTTP sessions
It is required that the methods on implementations of this interface be thread safe.
Generic interface for making HTTP client requests
Configuration object for creating a HttpClient
maximum permissible length of the initial response line
maximum combined length of the headers
whether to be lenient in HTTP/1.x parsing
AsynchronousChannelGroup used to multiplex connections on
SSLContext to use for secure connections
Representation of a concrete HTTP session
Standard HTTP request
HTTP request method
function which returns the next chunk of the request body. Termination is
signaled by an empty
ByteBuffer as determined by
The prelude of a standard HTTP response
Response status code
Response message. This has no meaning for the protocol, its purely for human enjoyment.
General configuration options for http servers
The basic type that represents a HTTP service
Future returned by the
RouteAction resolves, server
implementations are free to forcibly close the request body.
Response generator for HTTP servers
Incomplete collection of header names, all lower case for easy compatibility with HTTP/2.