A microframework based on Hyper providing traits to:
http::request::Parts
with query parameter deserialization & cookie parsinghyper::Body
with form deserialization (and optional CSRF protection)http::response::Builder
with methods to set & delete cookies and set the Content-TypeFurthermore Sputnik provides what's necessary to implement signed & expiring cookies with the expiry date encoded into the signed cookie value, providing a more lightweight alternative to JWT if you don't need interoperability.
Sputnik does not handle routing. For most web applications match
ing on
(method, path) suffices. If you need path variables, you can use one of the
many router crates.
Sputnik encourages you to create your own error enum and implement From
conversions for every error type, which you want to short-circuit with the ?
operator. This can be easily done with thiserror
because Sputnik restricts its error types to the 'static
lifetime.
```rust use std::convert::Infallible; use hyper::service::{servicefn, makeservice_fn}; use hyper::{Method, Server, StatusCode, Body}; use hyper::http::request::Parts; use hyper::http::response::Builder; use serde::Deserialize; use sputnik::{mime, request::{SputnikParts, SputnikBody}, response::SputnikBuilder}; use sputnik::request::CsrfProtectedFormError;
type Response = hyper::Response
;enum Error { #[error("page not found")] NotFound(String), #[error("{0}")] CsrfError(#[from] CsrfProtectedFormError) }
fn rendererror(err: Error) -> (StatusCode, String) { match err { Error::NotFound(msg) => (StatusCode::NOTFOUND, msg), Error::CsrfError(err) => (StatusCode::BADREQUEST, err.tostring()), } }
async fn route(req: &mut Parts, body: Body) -> Result
async fn getform(req: &mut Parts) -> Result
struct FormData {text: String}
async fn postform(req: &mut Parts, body: Body) -> Result
async fn service(req: hyper::Request
async fn main() { let service = makeservicefn(move || { async move { Ok::<_, hyper::Error>(servicefn(move |req| { service(req) })) } });
let addr = ([127, 0, 0, 1], 8000).into();
let server = Server::bind(&addr).serve(service);
println!("Listening on http://{}", addr);
server.await;
} ```
After a successful authentication you can build a session id cookie for example as follows:
rust
let expiry_date = OffsetDateTime::now_utc() + Duration::hours(24);
let mut cookie = Cookie::new("userid",
key.sign(
&encode_expiring_claim(&userid, expiry_date)
));
cookie.set_secure(Some(true));
cookie.set_expires(expiry_date);
cookie.set_same_site(SameSite::Lax);
resp.set_cookie(cookie);
This session id cookie can then be retrieved and verified as follows:
rust
let userid = req.cookies().get("userid")
.ok_or_else(|| "expected userid cookie".to_owned())
.and_then(|cookie| key.verify(cookie.value())
.and_then(|value| decode_expiring_claim(value).map_err(|e| format!("failed to decode userid cookie: {}", e)));
Tip: If you want to store multiple claims in the cookie, you can (de)serialize a struct with serde_json. This approach can pose a lightweight alternative to JWT, if you don't care about the standardization aspect.