NIOHTTP1

The components of a HTTP request from the view of a HTTP client.

The components of a HTTP response from the view of a HTTP client.

A ByteToMessageDecoder used to decode HTTP requests. See the documentation on HTTPDecoder for more.

A ByteToMessageDecoder used to decode HTTP/1.x responses. See the documentation on HTTPDecoder for more.

The components of a HTTP request from the view of a HTTP server.

The components of a HTTP response from the view of a HTTP server.

Configuration required to configure a HTTP client pipeline for upgrade.

Errors that can be raised while parsing HTTP/1.1.

The parts of a complete HTTP message, either request or response.

A HTTP response status code.

Errors that may be raised by the HTTPServerProtocolUpgrader.

User events that may be fired by the HTTPServerProtocolUpgrader.

Strategy to use when a HTTPDecoder is removed from a pipeline after a HTTP upgrade was detected.

A representation of a block of HTTP header fields.

A representation of the request line and header fields of a HTTP request.

A representation of the status line and header fields of a HTTP response.

A structure representing a HTTP version.

The parts of a complete HTTP response from the view of the client.

Errors that may be raised by the HTTPClientProtocolUpgrader.

Errors thrown by HTTPRequestDecoder and HTTPResponseDecoder in addition to HTTPParserError.

The parts of a complete HTTP response from the view of the client.

Strategy to use when a HTTPDecoder receives an informational HTTP response (1xx except 101)

A ChannelInboundHandler that parses HTTP/1-style messages, converting them from unstructured bytes to a sequence of HTTP messages.

A ChannelOutboundHandler that can serialize HTTP requests.

A ChannelOutboundHandler that can serialize HTTP responses.

A ChannelHandler that handles HTTP pipelining by buffering inbound data until a response has been sent.

A simple channel handler that catches errors emitted by parsing HTTP requests and sends 400 Bad Request responses.

A server-side channel handler that receives HTTP requests and optionally performs a HTTP-upgrade. Removes itself from the channel pipeline after the first inbound request on the connection, regardless of whether the upgrade succeeded or not.

A ChannelInboundHandler that handles HTTP chunked HTTPClientResponsePart messages by aggregating individual message chunks into a single NIOHTTPClientResponseFull.

A client-side channel handler that sends a HTTP upgrade handshake request to perform a HTTP-upgrade. When the first HTTP request is sent, this handler will add all appropriate headers to perform an upgrade to the a protocol. It may add headers for a set of protocols in preference order. If the upgrade fails (i.e. response is not 101 Switching Protocols), this handler simply removes itself from the pipeline. If the upgrade is successful, it upgrades the pipeline to the new protocol.

A ChannelInboundHandler that handles HTTP chunked HTTPServerRequestPart messages by aggregating individual message chunks into a single NIOHTTPServerRequestFull.

An object that implements HTTPServerProtocolUpgrader knows how to handle HTTP upgrade to a protocol on a server-side channel.

An object that implements NIOHTTPClientProtocolUpgrader knows how to handle HTTP upgrade to a protocol on a client-side channel. It has the option of denying this upgrade based upon the server response.