Scala wrapper around Netty cookies.
Adapt cookies of a Message to a mutable Map where cookies are indexed by their name.
Mutable message headers map.
The compression level to use. If passed the default value (-1) then use TextualContentCompressor which will compress text-like content-types with the default compression level (6). Otherwise, use HttpContentCompressor for all content-types with specified compression level.
The maximum size of the inbound request an HTTP server constructed with
this codec can receive (default is 5 megabytes). Should be less than 2 gigabytes (up to
Int.MaxValue
bytes). Use streaming/chunked requests to handle larger messages.
The maximum size of the inbound response an HTTP client constructed with
this codec can receive (default is 5 megabytes). Should be less than 2 gigabytes (up to
Int.MaxValue
bytes). Use streaming/chunked requests to handle larger messages.
Streaming allows applications to work with HTTP messages
that have large (or infinite) content bodies. When this flag is set to
true
, the message content is available through a com.twitter.io.Reader,
which gives the application a handle to the byte stream. If false
, the
entire message content is buffered into a com.twitter.io.Buf.
Trait HttpMuxHandler is used for service-loading HTTP handlers.
A service that dispatches incoming requests to registered handlers.
A service that dispatches incoming requests to registered handlers. In order to choose which handler to dispatch the request to, we take the path of the request and match it with the patterns of the pre-registered handlers. The pattern matching follows these rules:
NOTE: When multiple pattern matches exist, the longest pattern wins.
Mutable-Map-backed HeaderMap
Map-backed ParamMap.
Rich Message
Rich Message
Base class for Request and Response. There are both input and output methods, though only one set of methods should be used.
Represents the HTTP method.
Represents the HTTP method.
For Java-friendly enums, see com.twitter.finagle.http.Methods.
Request parameter map.
Request parameter map.
This is a multi-map. Use getAll() get all values for a key.
Rich HttpRequest.
Rich HttpRequest.
Use RequestProxy to create an even richer subclass.
HttpRequest-backed param map.
HttpRequest-backed param map. Handle parameters in the URL and form encoded body. Multipart forms are not supported (not needed, could be abusive).
This map is a multi-map. Use getAll() to get all values for a key.
Proxy for Request.
Proxy for Request. This can be used to create a richer request class that wraps Request without exposing the underlying netty http type.
Rich HttpResponse
Convert exceptions to BadHttpRequests
Represents an HTTP status code.
Represents an HTTP status code.
The set of commonly known HTTP status codes have an associated reason phrase
(see reasons
). We don't provide a way to set the reason phrase because:
- it simplifies construction (users only supply the code) - it avoids the need to validate user-defined reason phrases - it omits the possibility of statuses with duplicate reason phrases
The only downside is that we lose the ability to create custom statuses with "vanity" reason phrases, but this should be tolerable.
For Java-friendly enums, see com.twitter.finagle.http.Statuses.
Adds the host headers to for TLS-enabled requests.
Represents the HTTP version.
Represents the HTTP version.
For Java-friendly enums, see com.twitter.finagle.http.Versions.
Empty ParamMap
Singleton default multiplex service.
Singleton default multiplex service.
HttpMuxers for Java compatibility APIs.
Java compatibility APIs for HttpMuxer.
Factory for com.twitter.finagle.http.RequestBuilder instances
A SPNEGO HTTP authenticator as defined in https://tools.ietf.org/html/rfc4559, which gets its credentials from a provided CredentialSource...
A SPNEGO HTTP authenticator as defined in https://tools.ietf.org/html/rfc4559, which gets its credentials from a provided CredentialSource... usually JAAS.
Adapt cookies of a Message to a mutable Map where cookies are indexed by their name. Requests use the Cookie header and Responses use the Set-Cookie header. If a cookie is added to the CookieMap, a header is automatically added to the Message. You can add the same cookie more than once. Use getAll to retrieve all of them, otherwise only the first one is returned. If a cookie is removed from the CookieMap, a header is automatically removed from the message