7 unstable releases

new 0.4.0 Oct 31, 2024
0.3.1 Jul 19, 2024
0.3.0 Jan 10, 2024
0.2.1 Dec 14, 2023
0.1.1 Nov 20, 2023

#353 in HTTP server

Download history 8/week @ 2024-07-04 124/week @ 2024-07-18 65/week @ 2024-07-25 47/week @ 2024-08-01 31/week @ 2024-08-08 5/week @ 2024-08-15 39/week @ 2024-09-12 44/week @ 2024-09-19 43/week @ 2024-09-26 19/week @ 2024-10-03 30/week @ 2024-10-10 10/week @ 2024-10-17

115 downloads per month

Apache-2.0

14KB
144 lines

http-whatever

CI

A Thread-safe version of snafu::Whatever, which also allows for structured message strings giving HTTP status code and application domain qualifiers, and allows an Error to be turned into an http::Response.

I fully admit that this flies in the face of "type-oriented" error handling, but I really do feel that that is overkill for most HTTP applications where one error (or one error chain) is the most you will get out of any request/response cycle, and the goals are simply:

a. Tell the user what went wrong with a standard HTTP status and message, and b. Log the error (chain) for further investigation if necessary

To that end, this allows you to use the "whatever..." context features from snafu while still categorizing your errors and avoiding the boilerplate of creating error HTTP responses from those errors.

Examples

Basic use ala snafu::Whatever.

use http_whatever::prelude::*;
fn parse_uint(uint_as_str: &str) -> Result<usize, HttpWhatever> {
    uint_as_str.parse().whatever_context("400:RequestContent:Bad value")?
}

Using the macro

use http_whatever::prelude::*;
fn parse_uint(uint_as_str: &str) -> Result<usize, HttpWhatever> {
    uint_as_str.parse().whatever_context(http_err!(400,uint_as_str,"Bad input"))?
}

Dependencies

~1–1.5MB
~29K SLoC