rust-web-server 18.9.1

Single-binary web server and reverse proxy: automatic HTTPS (Let's Encrypt), HTTP/1.1, HTTP/2 and HTTP/3, load balancing, auth and rate limiting, configured in one TOML file. Also a Rust library: routing, middleware, MCP server, ORM, background jobs. No hyper, no Tower; HTTP/2 and HTTP/3 framing via h2 and quinn.
Documentation 
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

//! A dependency-free JSON parser and serializer.
//!
//! You describe a struct and implement [`New`](crate::core::New),
//! [`FromJSON`](object::FromJSON) and [`ToJSON`](object::ToJSON) for it; the trait bodies call the module's helpers
//! for each property. Nested objects and arrays are supported. It is not a
//! validator or formatter, but invalid input is an error, not a panic.
//! Submodules: [`object`], [`array`], [`property`]; examples live in their
//! `tests`/`example_*` modules (objects, nested objects, arrays of every scalar
//! type, arrays of objects).
//!
//! With the `serde` feature, `Json<T>` extracts a `Deserialize` type
//! from a request body and turns a `Serialize` type into an `application/json`
//! response — use that unless you want the explicit, macro-free mapping.
//!
//! # FAQ
//!
//! - **Line endings.** The parser doesn't care about `\n` vs `\r\n`;
//!   `to_json_string` writes `\r\n`, so compare against `\r\n` text in tests.
//! - **No pretty-printing.** `to_json_string` adds line breaks but doesn't indent
//!   nested values.
//! - **Why `New`?** Parsing an array has to create instances of your struct.
//! - **Mixed-type arrays** (`[1, true, "x"]`, tuples) don't map to one struct
//!   type; model them as an array of objects, or split the raw array with
//!   `RawUnprocessedJSONArray::split_into_vector_of_strings` and parse each item.
//! - **Numbers** are `i128` and `f64` (JSON has one number type); cast in your
//!   `FromJSON` if you need smaller types. `f64` has the usual binary rounding
//!   (`4356.257` reads back as `4356.2569999999996`) — store money as integer
//!   cents, or round when formatting.
//! - **Enums** have no JSON form: keep a string/integer property and map it to
//!   your enum in `FromJSON`/`ToJSON`.

#[cfg(test)]
mod tests;
pub mod property;
pub mod array;
pub mod object;

#[cfg(feature = "serde")]
mod extractor;
#[cfg(feature = "serde")]
pub use extractor::Json;

// TODO: wip

pub struct JSONType {
    pub string: &'static str,
    pub boolean: &'static str,
    pub object: &'static str,
    pub array: &'static str,
    pub integer: &'static str,
    pub number: &'static str,
    pub null: &'static str,
}

pub const JSON_TYPE: JSONType = JSONType{
    string: "String",
    boolean: "bool",
    object: "object",
    array: "array",
    integer: "i128",
    number: "f64",
    null: "null",
};