domain
and path
may be null.
Adapt cookies of a Message to a mutable Map where cookies are indexed by their name.
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
Mutable message headers map.
Mutable message headers map.
Header names are case-insensitive. For example, get("accept")
is the same as
get("Accept").
The map is a multi-map. Use getAll to get all values for a key. Use add to append a key-value.
This structure isn't thread-safe. Any concurrent access should be synchronized externally.
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.
The method is a case-sensitive string defined as part of the request line of the HTTP protocol.
https://tools.ietf.org/html/rfc7230#section-3.1.1
For Java-friendly enums, see com.twitter.finagle.http.Methods.
Request parameter map.
Request parameter map.
This is a persistent (immutable) multi-map.
Use getAll()
to get all values for a key.
Rich HttpRequest.
Rich HttpRequest.
Use RequestProxy to create an even richer subclass.
Http Request-backed ParamMap. This ParamMap contains both parameters provided as part of the request URI and parameters provided as part of the request body.
Request body parameters are considered if the following criteria are true:
Proxy for Request.
Proxy for Request. This can be used to create a richer request class.
Rich HttpResponse
Proxy for Response.
Proxy for Response. This can be used to create a richer response class.
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.
The Message was too long to be handled correctly
Represents an immutable URI.
Represents the HTTP version.
Represents the HTTP version.
For Java-friendly enums, see com.twitter.finagle.http.Versions.
Empty ParamMap