Package kong.unirest.core
package kong.unirest.core
-
ClassDescriptionBodyPart<T>Cache interface for response cachingInterface for the cache key which can be implemented by consumers The key should implement equals and hashCode It must must return the time the key was created.A functional interface to generate a cache keyCallback<T>The client that does the work.Represents a cookie parsed from the set-cookie header per https://tools.ietf.org/html/rfc6265 note that the RFC is awful.Represents a collection of cookies with some helper methods for parsing and getting cookieStandard cookie specifications supported by Unirest.A failed response you COULD return if you want to live in a house of lies.GenericType<T>Parts of this file were taken from Jackson/core TypeReference under the Apache License: Apache (Software) License, version 2.0 ("the License").Constants enumerating the HTTP headers.HttpRequest<R extends HttpRequest>The primary request builder used to create a request.A summary of a request about to be performedA request Builder for POST and PUT operations with a body.HttpResponse<T>A Summary of rhe responseEach configuration of Unirest has an interceptor.A metric context for the current requestA non-exclusive list of the most popular mime content typesRepresents a multi-part body builder for a request.Interface for object mappers that can transform response bodies to other structures.PagedList<T>Class for building a URI with query paramsA ProgressMonitor is a functional interface which can be passed to unirest for the purposes of monitoring uploads and downloads.The Raw Response represents the response before any mapping or consumption of the content.A Strategy for performing retries.A standard implementation of the RetryStrategy which follows spec based Retry-After logic - Will attempt a retry on any 301, 429, 503, or 529 response which is accompanied by a Retry-After headerA UniMetric is a factory for producing a MetricContext this will be called just before any Http RequestA Instance of the unirest runtime, you can have many of these but it is the config and its clients where all the action happens.An exception which prevents Unirest from attempting to recover the body from a failed response / parsing errorJust a silly little class that holds on to the socket and listener