Remove error_on_non_2xx. (#272)
After the recent changes in #257, it's probably not necessary. It's now quite easy to use a match statement to extract responses for certain status codes, or all status codes. Add documentation on how to turn a status code error back into a Response.
This commit is contained in:
@@ -82,6 +82,12 @@
|
||||
//! # fn main() {}
|
||||
//! ```
|
||||
//!
|
||||
//! ## Error handling
|
||||
//!
|
||||
//! ureq returns errors via `Result<T, ureq::Error>`. That includes I/O errors,
|
||||
//! protocol errors, and status code errors (when the server responded 4xx or
|
||||
//! 5xx). More details on the [Error] type.
|
||||
//!
|
||||
//! ## Features
|
||||
//!
|
||||
//! To enable a minimal dependency tree, some features are off by default.
|
||||
|
||||
Reference in New Issue
Block a user