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 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277
#![deny(missing_docs)] #![deny(missing_debug_implementations)] #![cfg_attr(test, deny(warnings))] #![cfg_attr(docs_rs_workaround, feature(extern_prelude))] #![doc(html_root_url = "https://docs.rs/reqwest/0.9.5")] //! # reqwest //! //! The `reqwest` crate provides a convenient, higher-level HTTP Client. //! //! It handles many of the things that most people just expect an HTTP client //! to do for them. //! //! - Uses system-native TLS //! - Plain bodies, JSON, urlencoded, multipart //! - Customizable redirect policy //! - Proxies //! - Cookies (only rudimentary support, full support is TODO) //! //! The rudimentary cookie support means that the cookies need to be manually //! configured for every single request. In other words, there's no cookie jar //! support as of now. The tracking issue for this feature is available //! [on GitHub][cookiejar_issue]. //! //! The `reqwest::Client` is synchronous, making it a great fit for //! applications that only require a few HTTP requests, and wish to handle //! them synchronously. //! //! ## Making a GET request //! //! For a single request, you can use the [`get`][get] shortcut method. //! //! ```rust //! # use reqwest::{Error, Response}; //! //! # fn run() -> Result<(), Error> { //! let body = reqwest::get("https://www.rust-lang.org")? //! .text()?; //! //! println!("body = {:?}", body); //! # Ok(()) //! # } //! ``` //! //! Additionally, reqwest's [`Response`][response] struct implements Rust's //! `Read` trait, so many useful standard library and third party crates will //! have convenience methods that take a `Response` anywhere `T: Read` is //! acceptable. //! //! **NOTE**: If you plan to perform multiple requests, it is best to create a //! [`Client`][client] and reuse it, taking advantage of keep-alive connection //! pooling. //! //! ## Making POST requests (or setting request bodies) //! //! There are several ways you can set the body of a request. The basic one is //! by using the `body()` method of a [`RequestBuilder`][builder]. This lets you set the //! exact raw bytes of what the body should be. It accepts various types, //! including `String`, `Vec<u8>`, and `File`. If you wish to pass a custom //! Reader, you can use the `reqwest::Body::new()` constructor. //! //! ```rust //! # use reqwest::Error; //! # //! # fn run() -> Result<(), Error> { //! let client = reqwest::Client::new(); //! let res = client.post("http://httpbin.org/post") //! .body("the exact body that is sent") //! .send()?; //! # Ok(()) //! # } //! ``` //! //! ### Forms //! //! It's very common to want to send form data in a request body. This can be //! done with any type that can be serialized into form data. //! //! This can be an array of tuples, or a `HashMap`, or a custom type that //! implements [`Serialize`][serde]. //! //! ```rust //! # use reqwest::Error; //! # //! # fn run() -> Result<(), Error> { //! // This will POST a body of `foo=bar&baz=quux` //! let params = [("foo", "bar"), ("baz", "quux")]; //! let client = reqwest::Client::new(); //! let res = client.post("http://httpbin.org/post") //! .form(¶ms) //! .send()?; //! # Ok(()) //! # } //! ``` //! //! ### JSON //! //! There is also a `json` method helper on the [`RequestBuilder`][builder] that works in //! a similar fashion the `form` method. It can take any value that can be //! serialized into JSON. //! //! ```rust //! # use reqwest::Error; //! # use std::collections::HashMap; //! # //! # fn run() -> Result<(), Error> { //! // This will POST a body of `{"lang":"rust","body":"json"}` //! let mut map = HashMap::new(); //! map.insert("lang", "rust"); //! map.insert("body", "json"); //! //! let client = reqwest::Client::new(); //! let res = client.post("http://httpbin.org/post") //! .json(&map) //! .send()?; //! # Ok(()) //! # } //! ``` //! //! ## Optional Features //! //! The following are a list of [Cargo features][cargo-features] that can be //! enabled or disabled: //! //! - **default-tls** *(enabled by default)*: Provides TLS support via the //! `native-tls` library to connect over HTTPS. //! - **hyper-011**: Provides support for hyper's old typed headers. //! //! //! [hyper]: http://hyper.rs //! [client]: ./struct.Client.html //! [response]: ./struct.Response.html //! [get]: ./fn.get.html //! [builder]: ./struct.RequestBuilder.html //! [serde]: http://serde.rs //! [cookiejar_issue]: https://github.com/seanmonstar/reqwest/issues/14 //! [cargo-features]: https://doc.rust-lang.org/stable/cargo/reference/manifest.html#the-features-section extern crate base64; extern crate bytes; extern crate encoding_rs; #[macro_use] extern crate futures; extern crate http; extern crate hyper; #[cfg(feature = "hyper-011")] pub extern crate hyper_old_types as hyper_011; #[cfg(feature = "default-tls")] extern crate hyper_tls; #[macro_use] extern crate log; extern crate libflate; extern crate mime; extern crate mime_guess; #[cfg(feature = "default-tls")] extern crate native_tls; extern crate serde; #[cfg(test)] #[macro_use] extern crate serde_derive; extern crate serde_json; extern crate serde_urlencoded; extern crate tokio; #[cfg_attr(feature = "default-tls", macro_use)] extern crate tokio_io; extern crate url; extern crate uuid; pub use hyper::header; pub use hyper::Method; pub use hyper::{StatusCode, Version}; pub use url::Url; pub use url::ParseError as UrlError; pub use self::client::{Client, ClientBuilder}; pub use self::error::{Error, Result}; pub use self::body::Body; pub use self::into_url::IntoUrl; pub use self::proxy::Proxy; pub use self::redirect::{RedirectAction, RedirectAttempt, RedirectPolicy}; pub use self::request::{Request, RequestBuilder}; pub use self::response::Response; #[cfg(feature = "default-tls")] pub use self::tls::{Certificate, Identity}; // this module must be first because of the `try_` macro #[macro_use] mod error; mod async_impl; mod connect; #[cfg(feature = "default-tls")] mod connect_async; mod body; mod client; mod into_url; mod proxy; mod redirect; mod request; mod response; #[cfg(feature = "default-tls")] mod tls; mod wait; pub mod multipart; /// An 'async' implementation of the reqwest `Client`. /// /// Relies on the `futures` crate, which is unstable, hence this module /// is **unstable**. pub mod async { pub use ::async_impl::{ Body, Chunk, Decoder, Client, ClientBuilder, Request, RequestBuilder, Response, ResponseBuilderExt, }; } /// Shortcut method to quickly make a `GET` request. /// /// See also the methods on the [`reqwest::Response`](./struct.Response.html) /// type. /// /// **NOTE**: This function creates a new internal `Client` on each call, /// and so should not be used if making many requests. Create a /// [`Client`](./struct.Client.html) instead. /// /// # Examples /// /// ```rust /// # fn run() -> Result<(), reqwest::Error> { /// let body = reqwest::get("https://www.rust-lang.org")? /// .text()?; /// # Ok(()) /// # } /// # fn main() { } /// ``` /// /// # Errors /// /// This function fails if: /// /// - native TLS backend cannot be initialized /// - supplied `Url` cannot be parsed /// - there was an error while sending request /// - redirect loop was detected /// - redirect limit was exhausted pub fn get<T: IntoUrl>(url: T) -> ::Result<Response> { Client::new() .get(url) .send() } fn _assert_impls() { fn assert_send<T: Send>() {} fn assert_sync<T: Sync>() {} fn assert_clone<T: Clone>() {} assert_send::<Client>(); assert_sync::<Client>(); assert_clone::<Client>(); assert_send::<Request>(); assert_send::<RequestBuilder>(); assert_send::<Response>(); assert_send::<Error>(); assert_sync::<Error>(); }