1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
//! HTTP transport abstraction and request helpers.
//!
//! Adapters never touch an HTTP client directly: they build an
//! [`HttpRequest`], hand it to an [`HttpTransport`] and interpret the
//! [`HttpResponse`] through [`ResponseHandler`]s. The request helpers in this
//! module ([`post_json`], [`get`], ...) tie those pieces together and map
//! transport failures to `ApiCallError`.
pub use DEFAULT_MAX_RESPONSE_BYTES;
pub use read_body;
pub use BinaryResponseHandler;
pub use BinaryStreamResponseHandler;
pub use EventSourceResponseHandler;
pub use Handled;
pub use JsonErrorResponseHandler;
pub use JsonResponseHandler;
pub use ParseResult;
pub use ResponseContext;
pub use ResponseHandler;
pub use ResponseHandlers;
pub use StatusCodeErrorResponseHandler;
pub use TextResponseHandler;
pub use binary_response_handler;
pub use binary_stream_response_handler;
pub use event_source_response_handler;
pub use json_error_response_handler;
pub use json_response_handler;
pub use parse_json_chunk;
pub use status_code_error_response_handler;
pub use text_response_handler;
pub use JsonLinesResponseHandler;
pub use json_lines_response_handler;
pub use MultipartForm;
pub use MultipartPart;
pub use ApiResponse;
pub use delete;
pub use get;
pub use post_bytes;
pub use post_form;
pub use post_json;
pub use send;
pub use RequestBody;
pub use ReqwestTransport;
pub use default_transport;
pub use BodyStream;
pub use HttpRequest;
pub use HttpResponse;
pub use HttpTransport;
pub use ResponseHead;
pub use SharedTransport;
pub use TransportError;
pub use TransportErrorKind;