# Package org.apache.http

Core HTTP components based on the blocking I/O model.

See: Description

Interface Summary
Interface | Description
--- | ---
ConnectionReuseStrategy | Interface for deciding whether a connection can be re-used for subsequent requests and should be kept alive.
FormattedHeader | An HTTP header which is already formatted.
Header | Represents an HTTP header field.
HeaderElement | One element of an HTTP `header` value consisting of a name / value pair and a number of optional name / value parameters.
HeaderElementIterator | A type-safe iterator for `HeaderElement` objects.
HeaderIterator | A type-safe iterator for `Header` objects.
HttpClientConnection | A client-side HTTP connection, which can be used for sending requests and receiving responses.
HttpConnection | A generic HTTP connection, useful on client and server side.
HttpConnectionFactory<T extends HttpConnection> | Factory for `HttpConnection` instances.
HttpConnectionMetrics | The point of access to the statistics of an `HttpConnection`.
HttpEntity | An entity that can be sent or received with an HTTP message.
HttpEntityEnclosingRequest | A request with an entity.
HttpInetConnection | An HTTP connection over the Internet Protocol (IP).
HttpMessage | HTTP messages consist of requests from client to server and responses from server to client.
HttpRequest | A request message from a client to a server includes, within the first line of that message, the method to be applied to the resource, the identifier of the resource, and the protocol version in use.
HttpRequestFactory | A factory for `HttpRequest` objects.
HttpRequestInterceptor | HTTP protocol interceptor is a routine that implements a specific aspect of the HTTP protocol.
HttpResponse | After receiving and interpreting a request message, a server responds with an HTTP response message.
HttpResponseFactory | A factory for `HttpResponse` objects.
HttpResponseInterceptor | HTTP protocol interceptor is a routine that implements a specific aspect of the HTTP protocol.
HttpServerConnection | A server-side HTTP connection, which can be used for receiving requests and sending responses.
HttpStatus | Constants enumerating the HTTP status codes.
NameValuePair | A name / value pair parameter used as an element of HTTP messages.
ReasonPhraseCatalog | Interface for obtaining reason phrases for HTTP status codes.
RequestLine | The Request-Line begins with a method token, followed by the Request-URI and the protocol version, and ending with CRLF.
StatusLine | The first line of a Response message is the Status-Line, consisting of the protocol version followed by a numeric status code and its associated textual phrase, with each element separated by SP characters.
TokenIterator | An iterator for `String` tokens.

Class Summary
Class | Description
--- | ---
Consts | Commons constants.
HttpHeaders | Constants enumerating the HTTP headers.
HttpHost | Holds all of the variables needed to describe an HTTP connection to a host.
HttpVersion | Represents an HTTP version.
ProtocolVersion | Represents a protocol version.

Exception Summary
Exception | Description
--- | ---
ConnectionClosedException | Signals that the connection has been closed unexpectedly.
ContentTooLongException | Signals that HTTP entity content is too long.
HttpException | Signals that an HTTP exception has occurred.
MalformedChunkCodingException | Signals a malformed chunked stream.
MessageConstraintException | Signals a message constraint violation.
MethodNotSupportedException | Signals that an HTTP method is not supported.
NoHttpResponseException | Signals that the target server failed to respond with a valid HTTP response.
ParseException | Signals a parse error.
ProtocolException | Signals that an HTTP protocol violation has occurred.
TruncatedChunkException | Signals a truncated chunk in a chunked stream.
UnsupportedHttpVersionException | Signals an unsupported version of the HTTP protocol.

## Package org.apache.http Description

Core HTTP components based on the blocking I/O model. These deal with the fundamental things required for using the HTTP protocol, such as representing a `message` including it's `headers` and optional `entity`, and `connections` over which messages are sent. In order to prepare messages before sending or after receiving, there are interceptors for `requests` and `responses`.